System and method for paying a merchant by a registered user using a cellular telephone account

ABSTRACT

A system and method allows users to make purchases by charging or funding a prepaid debit card with their cell phone accounts by simulating a user roaming with their mobile device.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of attorney docket number 1675, U.S.Patent Application Ser. No. 61/281,892, entitled, “Method and Apparatusfor Paying a Merchant Using a Cellular Telephone Account” filed byMichael Brody on Nov. 23, 2009 and is a continuation in part of attorneydocket number 1665, U.S. patent application Ser. No. 12/583,151,entitled “System and Method for Paying a Merchant Using A CellularTelephone Account” Filed by Michael Brody, Roger Desai, and Sung Kim onAug. 14, 2009, which claims the benefit of U.S. Provisional ApplicationSer. No. 61/088,839 Entitled, “System for Enabling Mobile-BasedFinancial Transactions and Methods Thereof” Filed by Roger Desai on Aug.14, 2008, each having the same assignee as the present application, andeach is hereby incorporated by reference in its entirety.

FIELD OF THE INVENTION

The present invention is related to computer software and morespecifically to computer software for payment processing.

BACKGROUND OF THE INVENTION

It can be desirable to pay for items ordered online using a cellulartelephone account. The account may be either a prepaid account, in whichmoney is deposited in the account prior to purchasing goods or serviceswith that account, or a postpaid account, in which credit is extended tothe account holder for goods and services, usually to be paid by the endof the month.

Conventional solutions involve the user using a cell phone to dial anumber or sending an SMS text message to a short code (a shorter stringof digits with which an SMS text message may be addressed), which thenis charged against the user's cellular telephone account usingconventional methods. The number or short code corresponds to a fixedamount that will be charged to the user's cellular telephone account,similar to a 976 call.

Although this arrangement can be used for purchasing discrete productssuch as a soda from a vending machine, it does not provide the level offlexibility to use for purchasing from online merchants sellingdifferent-priced goods or services. It would be possible to usemultiples of each of several possible amounts by dialing the variouscombinations of messages or sending the various combinations of SMS textmessages to reach a desired amount, but such operation is cumbersome,and SMS messages are not fully reliable, making this arrangement moredifficult to use.

What is needed is a system and method that can charge a flexible amountto a user's prepaid or postpaid cellular telephone account, such as whenordering goods or services from an online merchant.

SUMMARY OF INVENTION

An operator of some or all of the system and method, referred to as acell phone payment processor, registers with cellular telephoneoperators and/or clearinghouses as a cellular telephone service roamingprovider. The system and method then receives a request from a merchant,such as an online merchant, to pay for goods or services the holder ofthe cellular telephone is in the process of ordering. The merchant orthe user supplies the user's cellular telephone number to the system andmethod. The user is validated, the transaction is checked for fraud orunacceptably high number of returns, their status as a prepaid accountor one that will be postpaid is identified, and the user's accountstatus and other information is determined and validated, includingidentifying the IMSI, a code associated with the SIM card that is usedto operate the cellular telephone. If the cell phone account is aprepaid account, a determination is made as to whether the balance issufficient for the amount to be charged, plus any additional amountrequired by the cell phone service provider. If so, the amount ischarged to that account by an operator of the system and method in themanner of a roaming service provider. If the user is postpaid, theaccount is charged also in the manner of a roaming service provider, anda description of the transaction is provided to the user's carrier,optionally via a clearinghouse. The merchant is informed of the payment,and then the merchant provides the goods or services ordered, forexample, by shipping them from one location to another, or providinggoods or services electronically over a network, or by taking an action,potentially having a physical effect, that causes a service to beprovided.

In one embodiment, if the user does not have a sufficient balance in aprepaid cell phone account, the system and method asks the user todeposit more funds in the account, informs the merchant that thetransaction should be held, and, when the balance is fully paid, informsthe merchant that payment has been received. The merchant then providesthe goods or services as described herein. If desired, a layaway planmay be set up that takes multiple payments from the user's cell phoneaccount until the amount of the transaction is paid in full, at whichpoint, the merchant is informed that payment has been provided and themerchant then provides the goods or services as described herein.

The user may use their cell phone account to purchase, or add value to,a prepaid debit card using the system and method of the presentinvention if the merchant does not offer payment by cell phone. The usermay then use the prepaid debit card at any merchant or online merchantthat accepts them. The user may instead receive a debit card or creditcard that is paid for using their cell phone account when any chargesare made to the card. The user need not receive a physical card, but mayinstead receive information that would be on the card, such as cardnumber, expiration date and a three digit code.

In one embodiment, when a user uses the system and method with a trustedmerchant, if the user is registered with that merchant and has beenauthenticated to the system and method when the user previously used thesystem and method with the trusted merchant, the user may be affordedprivileges, such as less or no authentication, or less or noverification of account balance or good standing of their account.

In one embodiment, the no merchant is involved, as a subscriber takesthe place of a merchant to transfer money to a different subscriber.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block schematic diagram of a conventional computer system.

FIG. 2, consisting of FIGS. 2A, 2B, and optionally, 2C, is a flowchartillustrating a method of charging a user's cellular telephone accountfor a purchase made from a merchant, such as an online merchantaccording to one embodiment of the present invention.

FIG. 3 is a method of settling cellular telephone roaming chargesaccording to one embodiment of the present invention.

FIG. 4 is a method of integrating a registration process into thecharging method of FIG. 2.

FIG. 5A is a method of paying for goods or services using a payment cardthat charges a user's cell phone account upon demands made to the cardaccording to one embodiment of the present invention.

FIG. 5B is a method of paying for goods or services using a prepaiddebit card funded through a user's cell phone account according to oneembodiment of the present invention.

FIG. 6 is a block schematic diagram of a system for paying for goods orservices using a cell phone account according to one embodiment of thepresent invention.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

The present invention may be implemented as computer software on aconventional computer system. Referring now to FIG. 1, a conventionalcomputer system 150 for practicing the present invention is shown.Processor 160 retrieves and executes software instructions stored instorage 162 such as memory, which may be Random Access Memory (RAM) andmay control other components to perform the present invention. Storage162 may be used to store program instructions or data or both. Storage164, such as a computer disk drive or other nonvolatile storage, mayprovide storage of data or program instructions. In one embodiment,storage 164 provides longer term storage of instructions and data, withstorage 162 providing storage for data or instructions that may only berequired for a shorter time than that of storage 164. Input device 166such as a computer keyboard or mouse or both allows user input to thesystem 150. Output 168, such as a display or printer, allows the systemto provide information such as instructions, data or other informationto the user of the system 150. Storage input device 170 such as aconventional floppy disk drive or CD-ROM drive accepts via input 172computer program products 174 such as a conventional floppy disk orCD-ROM or other nonvolatile storage media that may be used to transportcomputer instructions or data to the system 150. Computer programproduct 174 has encoded thereon computer readable program code devices176, such as magnetic charges in the case of a floppy disk or opticalencodings in the case of a CD-ROM which are encoded as programinstructions, data or both to configure the computer system 150 tooperate as described below.

In one embodiment, each computer system 150 is a conventional SUNMICROSYSTEMS ULTRA 10 workstation running the SOLARIS operating systemcommercially available from SUN MICROSYSTEMS, Inc. of Mountain View,Calif., a PENTIUM-compatible personal computer system such as areavailable from DELL COMPUTER CORPORATION of Round Rock, Tex. running aversion of the WINDOWS operating system (such as 95, 98, Me, XP, NT or2000) commercially available from MICROSOFT Corporation of Redmond Wash.or a Macintosh computer system running the MACOS or OPENSTEP operatingsystem commercially available from APPLE INCORPORATED of Cupertino,Calif. and the MOZILLA browser commercially available from MOZILLAFOUNDATION of Mountain View, Calif. or INTERNET EXPLORER browsercommercially available from MICROSOFT above, although other systems maybe used.

FIG. 2, consisting of FIGS. 2A, 2B and 2C are a flowchart illustrating amethod of processing payments by charging a cellular telephone accountover a network according to one embodiment of the present invention. Theparty performing at least some of the method illustrated in FIG. 2 isreferred to herein as a cell phone payment processor, and this partyarranges with cellular telephone operators and/or conventional cellulartelephone payment clearinghouses such as Syniverse or MACH to act as aprovider of cellular telephone roaming services, including internationalcellular telephone roaming services) in the same manner as a trueprovider of conventional cellular roaming services would. Roaming refersto providing service on a cellular telephone network to a subscriber ofa different cellular telephone service. The party providing the roamingservice does not have a contractual relationship with the user for theuse of the phone being used on their network, but may have arelationship with the user's cell phone operator for providing roamingservices. Other conventional roaming definitions may also be used.

In one embodiment, the cell phone payment processor, who is the partyarranging to act as a provider of roaming services, will not beproviding as much roaming service as payment processing services asdescribed herein. A party who provides more, or far more paymentprocessing services than actual cellular roaming services may bereferred to as a “sineroaming” roaming services provider. Such a partymay provide no actual conventional cellular roaming services at all. Inone embodiment, a sineroaming roaming services provider does not have acustomer relationship with some (in one embodiment), most (in anotherembodiment), or all of the subscribers of other cellular telephoneservices who use it for payment processing as described herein.

User Purchases and Checks Out.

To use the system and method of the present invention, a subscriber ofcellular services (the subscriber is referred to interchangably as the“user” and the “subscriber”) uses an online merchant to purchase goodsor services in a conventional fashion, and then checks out 212. In oneembodiment, each product is a product other than a mobile device-relatedproduct and each service is a service other than roaming or anothermobile-related service. In one embodiment, the purchase and check outmay be made via a conventional browser using the Internet. The browsermay be running on the same cellular telephone that the user uses forplacing calls, but the browser may instead be running on a conventionalcomputer system, such as a conventional personal computer system, onewhich has no connection to the user's cellular telephone that is evidentto the merchant.

In one embodiment, when the user checks out, the user is asked for theform of payment as part of step 212. Forms of payment may include creditcards as well as payment by cellular telephone. If the user selectspayment by cellular telephone 214, the user is requested to enter theircellular phone number and such information is received 216. (If the userselects a different form of payment, the selected other form of paymentis processed in a conventional fashion).

Any or all of the request for type of payment and the request andreceipt of the telephone number may be performed by the merchant, theparty who will perform some or all of the remainder of the steps of FIG.2 (i.e. the cell phone payment processor) or any other party.

The user may be referred (e.g. via a redirect or a link) to the party(the cell phone payment processor) who will perform some or all of theremainder of the steps of FIGS. 2A and 2B following any such actionsperformed by the merchant or other party. In one embodiment, themerchant refers the party with an identifier of the merchant, the amountof the transaction corresponding to the goods and services purchased,and optionally other information described below in the URL used torefer the user. If the merchant or a third party receives the telephonenumber, the telephone number may also be part of the referrerinformation. In one embodiment, referrer information is information tothe right of a slash (‘/’) that follows the domain name in the URL usedto refer the user. In another embodiment, the user is not referred, butall such information is provided (e.g. via a network such as theInternet) to the cell phone payment processor performing some or all ofthe remainder of the steps of FIGS. 2A and 2B. The referral or otherwiseproviding such information (i.e. to the cell phone payment processor)operates as a request by the merchant for payment for the goods orservices ordered. As described below, if some or all of the conditionsdescribed below are met, the request will be fulfilled via a charge tothe cell phone account corresponding to the telephone message.

Check to See the User has the Phone.

As a result of receiving the referral, an SMS text message is generatedand sent to the user's telephone 218 using the number the user provided,and the user is requested 220 to enter some or all of the text messagereceived using the web session that may have been referred, in order tocheck to see that the user of the web session has the telephone (whichis at least an indication that the user of the web session is thesubscriber corresponding to the phone).

The subscriber then provides such message or part via the web session,and the entered message is compared with the pertinent portion of themessage sent to the subscriber's telephone to see if a correspondence,such as a match, has occurred between those two pieces of data 222. If acorrespondence occurs 224, the method continues at step 230.

If a correspondence does not occur 224, an error is indicated 246, andthe method continues at step 212, where a different request is received.Indication of the error in step 246 may include telling the merchant whythe error was detected, for example, because the message was notreturned, or the account status was suspended or disabled as describedbelow. Step 246 may include referring the user to a special merchantpage.

Request Information about the Subscriber Account.

In one embodiment, while waiting for the user to provide the message asdescribed above, information about the account corresponding to thephone number entered is requested and received as part of step 220, forexample, from a roaming clearinghouse, such as MACH or Syniverse. In oneembodiment, the information may be requested from individual cellulartelephone service providers, such as by querying the service providerscorresponding to the country code of the cellular telephone numberreceived, in order or approximate order of market share until theservice provider indicates the phone number corresponds to an account ofone of its customers, or by requesting an identifier of the user'scellular telephone service provider (also referred to as an “operator”)from a clearinghouse, and then querying that operator.

To query in order or approximate order of market share, the cellulartelephone service providers corresponding to each of several or allcountry codes are identified, and market share or estimates of themarket share for each cellular telephone service provider is receivedfor each of the country codes for which cellular telephone serviceproviders were identified. When information about an accountcorresponding to a telephone number is desired, the country code isextracted from the telephone number, the cellular telephone serviceproviders that service that country code are identified using thoseidentified as described above, such cellular telephone service providersare ranked in decreasing order of market share, and information aboutthe account corresponding to the telephone number is requested from eachsuch provider in the ranked order until a response containing thedesired information as described below is received. The requests may bemade one at a time or several may be in progress at any given time, forexample, by querying the top three simultaneously, and if none of themresponds with an account status, querying the remainder of the providersin decreasing order one at a time until an account status is received.

In one embodiment, the information is requested from the clearinghouseusing the telephone number received, and the information requested andreceived may include an identifier of the cellular telephone operator,the status of the user's account (i.e. suspended or disabled) and phone(on or off), and the IMSI (International Mobile Subscriber ID) of theSIM card or other identifier of the telephone that allows the phone toidentify itself on the operator's network.

In one embodiment, the portion of step 220 that requests and retrievesinformation from the clearinghouse may be performed at a different time,such as after the user has successfully returned the message asdescribed above. In such embodiment, such portion of step 220 may beperformed only if the user has successfully returned the message and themethod continues at step 230. If the user does not successfully returnthe message, the method continues at step 246.

Fraud/Chargeback Check.

A fraud and chargeback check is optionally performed 230. In oneembodiment, the fraud check identifies the country in which the user isusing the Internet based on the IP address of the user and a databasematching IP addresses to the countries of origin, identifies the homecountry of the user based on the telephone number of that user and adatabase of country codes, identifies the country of the merchant (via adatabase) or the country in which the goods are being shipped (e.g. byasking the user for this information or receiving it from the merchantin the referrer information), and identifies whether the country inwhich the user is operating or roaming. In one embodiment, the countryhandling the user's most recent cell phone communication (which may be acall or the phone communicating with a cell tower to identify itslocation) is provided by the clearinghouse as part of step 220 above.Fraud is determined using these countries. For example, if the countrycorresponding to the user's phone number is different from the countryof the merchant or the country to which the goods are being shipped, andthat country is different from the country corresponding to the user'sIP address, fraud is indicated unless the user is roaming in thatcountry, in which case, fraud is not indicated. A score may be assignedbased on such factors, with scores adjusted based on the actualcountries involved. For example, if one or more of the countries isassociated with extreme poverty, a score more indicative of fraud may beassigned than if no such countries are involved. Fraud is detected ifthe score exceeds a threshold.

In one embodiment, the operator cell phone payment processor may querythe operator handling the call for the cell tower being used, and theuser's location may be more specifically identified based on thelocation of the cell tower.

The chargeback check checks for unacceptably high numbers of returns bya user corresponding to an IMSI. Each merchant may specify a thresholdnumber of chargebacks or chargebacks per unit of time or absolute valueof dollar amount of chargebacks or absolute value of dollar amount ofchargebacks per unit of time that are allowed by a user before this testfails for that user. A chargeback is a charge that results in themerchant funds being paid to the user, for example, due to a disputethat the user files with the transaction network. In one embodiment,only chargebacks for that merchant for the same customer are countedtowards the threshold and in another embodiment, all chargebacks for thesame IMSI are counted towards the threshold. In one embodiment, onlychargebacks to a merchant who sells merchandise (as opposed to a userwho is really just transferring money to a different subscriber) arecounted towards the threshold. All chargebacks are recorded by thesystem and method, and stored, associated with the IMSI, for at leastthe maximum unit of time, such as a year.

If fraud is detected, or the account status was received as negative(e.g. suspended or disabled) 232, or the chargebacks for the user exceedthe merchant's threshold, the method continues at step 246. Otherwise232, the method continues at step 234.

Determine if Prepaid or Post Paid Account.

A check is made 234 to the operator's prepaid platform to determine ifthe subscriber is a prepaid subscriber (e.g. the subscriber ordinarilypays in advance and service will be terminated if the balance fallsbelow zero or an amount near zero), or a postpaid subscriber (thesubscriber is issued credit for service, to be paid for after theservice is provided). In one embodiment, there may be differentplatforms for prepaid and postpaid subscribers. In other embodiments, asingle platform is used, with an indicator indicating whether thesubscriber is prepaid or postpaid, and the indicator is used todetermine whether the subscriber is prepaid or postpaid. A database ofoperators and platform locations maintained by the cell phone paymentprocessor may be used to locate the platform. Each operator may have itsown platform or platforms that it uses, the details of how to use suchplatform or platforms being received from the operator and stored in thedatabase.

If two platforms are used, the prepaid platform allows identification ofwhether a subscriber having a given phone number has a prepaid plan or apostpaid plan. The prepaid platform may identify the balance on theaccount, and the postpaid platform may identify the account status (e.g.in good standing, not in good standing, or closed). In one embodiment,all such information is available on a single platform. The platform maybe the same platform used to maintain account information or it may be aseparate platform from such platform, with information that is slightlyout of date.

In another embodiment, a roaming clearinghouse may provide informationthat can be used to determine whether the subscriber is prepaid orpostpaid and such clearinghouse is used to make the determination. Thedatabase may indicate which operators for which the clearinghouse shouldbe used and which operators provide access to their platforms and so theclearinghouse need not be used.

The telephone number or IMSI is used to identify the subscriber todetermine whether the subscriber is prepaid or postpaid on the platformor clearinghouse. In one embodiment, information is only suppliedindicating that the subscriber is a prepaid subscriber, and thus, if thesubscriber's account is not indicated as being prepaid, the subscriberis assumed to be postpaid, otherwise, the subscriber is prepaid. In oneembodiment, the database indicates whether this assumption should bemade for a given operator and it is made if so indicated in thedatabase.

In one embodiment, if the account is not located on the prepaidplatform, postpaid type is assumed and in another embodiment, if theaccount is not located on the prepaid platform, a postpaid platform isused to verify that the account is of a postpaid type. If the account islocated on the prepaid platform or is indicated, on a sharedprepaid/postpaid platform as being prepaid, the account type of prepaidis used for the user.

If the subscriber is a prepaid subscriber 236, the method continues atstep 238, and otherwise 236, the method continues at step 260 of FIG.2B.

Prepaid Accounts

At step 238, the balance of the prepaid user is requested and received,either from the operator, or from a clearinghouse such as MACH orSyniverse, for example, using the conventional CAMEL protocol, or usingother conventional middleware. The manner and details of making therequest may be stored in the database associated with each operator, andthe operator identified as described above is used to identify themanner and details of making this request. The details of how to makerequests of operators platforms are worked out with the operator, eachoperator may use a different technique.

In one embodiment, some or all operators require that a subscribermaintain a minimum balance, and so a charge that will cause thesubscriber's prepaid account to drop below the minimum balance will berefused by that subscriber's cell phone service provider. In oneembodiment, the amount that is available to be charged is returned aspart of the response to the balance request. In another embodiment, theminimum balance is returned with the balance request, or it may beotherwise requested and received. In still another embodiment, thedatabase may include the minimum balance for each of some or allcarriers, identified by trial and error (attempting to request theentire balance of an account, receiving a refusal, and then repeatedlybacking off by one cent and trying again and again, receiving refusalsuntil the charge is allowed, and then identifying the difference betweenthe charge allowed and the balance of the account as the minimumbalance), by asking each carrier, or, for each carrier, by recording thedifference between the amount requested and the balance in the accountfor that carrier, and identifying the minimum as the smallest differencebetween the amount requested and the balance that is allowed by thecarrier, when a difference a threshold amount less than that amount(e.g. one cent, or the smallest unit of measure regularly used by thecurrency corresponding to the carrier) has not been allowed by thecarrier.

If the balance is insufficient to support the charge received from themerchant 240, the method continues at step 246 and otherwise 240, themethod continues at step 264 of FIG. 2B.

In one embodiment, step 238 includes requesting a hold on thesubscriber's account in the amount of the charge (referred to as a“reserve”) so that future requests for the subscriber's balance, forexample by other roaming service providers, will produce the balance,less the amount of the reserve, so that the balance is not overdrawn bymultiple charges occurring prior to settlement. In such embodiment, thereserve may be released as part of step 246 if funds are insufficient,or it may be captured (i.e. committed) as part of step 264 to indicatethat settlement will occur. In one embodiment, the reserve may becaptured in part, with the remainder released if not fully used.

Virtual Layaway.

In one embodiment, step 280 of FIG. 2C follows the “no” branch of step240 of FIG. 2A. That is, if the user's prepaid balance is insufficient240, the method continues at step 280 of FIG. 2C.

At step 280, the subscriber is informed (e.g. via the web or a textmessage to the subscriber's phone) that his prepaid balance isinsufficient and instructed to increase the prepaid balance by at leastthe amount that would allow the transaction to proceed. In oneembodiment (not shown in the Figure), the subscriber may decline theoffer, the merchant is notified that the transaction should be aborted,and the method continues at step 212 of FIG. 2A.

In one embodiment, the user may set up a payment schedule instead of asingle payment, to allow the user to pay off the amount of the charge ininstallments. In such embodiment, the amount and schedule of suchpayments to be deducted from the user's account is requested andreceived 282.

In one embodiment, the merchant is informed 284 to hold the order, andthe merchant may either supply an order identifier or one is generatedand supplied to the merchant to allow the order to be referred to at afuture time as described herein. In one embodiment, when the merchantreceives the hold, the merchant may reserve inventory for the order, sothat it does not get sold out before the user can pay for it.

The method waits an amount of time, such as a day or the amount of timeto the first payment in the payment schedule received as describedabove, and the balance is requested and received from the user's cellphone account as described herein 286. If the balance is sufficient tomake the next scheduled payment (which may be the only payment) 288, themethod continues at step 290 in one embodiment, or step 294 in anotherembodiment as indicated by the dashed line in the Figure, in which caseonly a single payment is used. No input from the user is required tocause these steps to be performed, in one embodiment.

At step 290, the order is credited by the amount of the scheduledpayment or the entire amount and, if a scheduled payment was used, adetermination is made as to whether the total of credits for the ordermatches the amount of the order. The method additionally continues atstep 264 of FIG. 2B to begin the settlement process for the currentpayment amount or entire amount and also continues at step 292. If thetotal of credits for that order matches the amount of the order 292, themethod continues at step 294 and otherwise 292, continues at step 286.

At step 294 successful payment is indicated to the merchant and themerchant account is credited for the total amount, less a fee due theparty performing some or all of the steps of FIGS. 2A-2C and themerchant provides the goods or services as described herein.

If, after the amount of time the system waits, the balance isinsufficient, the method continues at step 246. In such embodiment, step246 may include crediting the user with the amount paid towards thetransaction.

In one embodiment, if the balance is insufficient, but there has been anamount already paid towards the transaction, and the number of times aninsufficient balance has been encountered since the last payment is lessthan a threshold, the method continues at step 286. In this manner,after the first payment is made, the user may be given more than oneattempt to provide payment. In one embodiment, as the end of the periodof time the method waits is approaching the end, the subscriber is senta text or e-mail message reminding them that the next payment will bededucted. Their prepaid balance may be requested and provided with suchmessage in one embodiment.

Post Paid Accounts.

At step 260, an indication of the customer's creditworthiness isrequested from the operator or a roaming clearinghouse, such as MACH orSyniverse. In one embodiment, to request the creditworthiness of thecustomer, the database is consulted for the details of making such arequest for the operator received as described above, and those detailsare followed by applying the telephone number of the subscriber to thedetails listed for the operator. Each operator may have a differenttechnique for obtaining this information. The response to the request isinterpreted in accordance with details for interpreting the response forthat operator in the database to determine if the subscriber iscreditworthy or not. The details and interpretation may be a function ofthe amount of the purchase, for example, with lower amounts beingprocessed according to one set of details and higher amounts beingprocessed according to a different set of details, all such details andthe threshold amounts causing one set of details to be used instead ofanother being stored in the database for each operator.

In one embodiment, a per transaction credit limit may be imposed foreach operator and stored in the database, and/or a credit limit may beused for all operators, and customers are not considered creditworthy ifthe transaction exceeds the applicable credit limit for that operator orfor all operators, whichever is lower.

If the subscriber is determined not to be creditworthy 262, the methodcontinues at step 246 of FIG. 2A, and otherwise 262, the methodcontinues at step 264.

Payment Processing.

At step 264, an entry is generated and either sent to a roamingclearinghouse, such as MACH or Syniverse or held until a number ofentries is received or an amount of time elapses, at which point thenumber of entries or the entries held until the amount of time elapsesare sent to the clearinghouse. An entry may be sent to the operator towhich it pertains in another embodiment, or a combination of sendingsome entries to a clearinghouse and other entries to operators may beused. In one embodiment, each entry includes the name or otheridentifier of the operator received as described above, the IMSIretrieved as described above, the amount of the transaction in thecurrency of the merchant, the amount in currency local to the operator,and a description received with the referrer information from themerchant as described above. The description may include the name of themerchant and a description of some or all of the goods and/or servicesordered in the transaction.

In one embodiment, the other identifier may include a TADIG number(Transferred Account Data Interchange Group number) of the operator,and/or the PMN (Public Mobile Network) code of the operator maintainedin the database of other operator information described herein.

In one embodiment, there are two amounts: one is the amount of thecharge to the subscriber and the other is the amount the subscriber'soperator should remit as payment to the clearinghouse or otherintermediary, the difference to be kept by that operator. This allowsthe operator to take a fee for collecting and providing the funds. Theuser will see the amount of the charge, but may not see, or even beaware of, the amount the operator is remitting. In one embodiment, theamount charged to the user is the amount charged by the merchant, withthe merchant collecting less than this amount, and in another embodimentthe amount charged to the user is an amount higher than the amountcharged by the merchant.

The clearinghouse or cell phone service provider converts 266 the entryinto a conventional TAP record used for roaming charges, including thedescription added to where the name of the roaming operator wouldordinarily have gone. The subscriber's operator may include thedescription on the invoice or statement of charges the subscriberreceives from that operator in paper form, or the invoice or statementof charges that is made available in web form, to allow the subscriberto identify the charge. Step 266 includes providing the TAP record orthe information that will be part of the TAP record to theclearinghouse. In one embodiment, step 266 includes generating aconventional CDR file of the charges and the user's operator that willbe used for settlement.

Each of the clearinghouses clears transactions for certain of theoperators, and if the clearinghouse to which the entry was sent does notclear transactions for the operator for that entry, it provides 268 thecorresponding TAP record to the other clearinghouse. The clearinghousethat clears such transactions provides 270 the TAP record to theoperator. The operator will charge the subscriber's telephone account inthe manner of a roaming service charge. Thus, even though no roamingservice was provided, the subscriber will see a roaming service chargeon his or her mobile telephone account resulting from the purchase ofgoods or services from a merchant, even though the goods may be anygoods, and may not be cell phone related goods, and services may not beconventional sell phone services, where voice text or data is carriedover a cell phone network in return for the charge.

A successful payment is indicated to the merchant and an amount equal tothe charge less a fee due the cell phone payment processor is creditedto the merchant's account and the charge or remittance amount is debitedfrom a bookkeeping account corresponding to the operator as describedabove, either in the local currency of the merchant (or the partyperforming at least some of the method of FIG. 2) or the subscriber orthe operator, or in conventional SDRs, a basket of currencies 272. Step272 may be performed at an earlier time, for example, after steps 262 or240. As part of step 272, as a result of receiving the indication ofsuccessful payment described above, the merchant then provides theordered goods, either by physically shipping them or providing themelectronically over a network such as the Internet. Services that wereordered may be provided by the merchant as part of step 272 byperforming a physical action or by sending information over a network,such as the cell phone network, for example, to the subscriber's mobiledevice. Providing goods or services in this fashion is referred toherein as “Performing a Goods or Services Action” or that the merchant“Performs a Goods or Service Action”. Performing a Goods or ServicesAction may include, without limitation, SMS or other mobile ticketing,in which a ticket to an event or another type of ticket is provided viaan SMS text message or other message sent to a mobile device, such as aUSSD message.

The method continues at step 212 (or the method may continue at step 212from step 264, with steps 266-270 operating as a separate, independentlyoperating process). Any number of transactions may be processed in thisfashion, and some transactions may be simultaneously processed withother transactions.

Although a single user and merchant is described above, the system andmethod allows multiple users purchasing from different merchants toprocess payments via a cellular telephone account in the same or similarfashion. Communication between the user, merchant, cell phone paymentprocessor and clearinghouses may be performed using the Internet. In oneembodiment, any communication described herein may be performed usingconventional SS7 techniques and using the conventional SS& protocol.

GSM Vs. CDMA.

The procedures described above refer to GSM phones. CDMA telephones mayuse a similar process, with CIBER replacing CAMEL or a TAP record. Inone embodiment, the database matches carriers to CDMA or GSM, and theappropriate protocols are used for each when the carrier is identifiedas described above. In another embodiment, the clearinghouse providesthe network type as part of step 220. In still another embodiment, theconventional APIs corresponding to each protocol are used until oneprovides an appropriate response. The API that works may be associatedwith the phone number in a subscriber database, and that API is usedfirst to attempt to reduce the number of API calls made, while allowingfor the possibility that the proper API for that phone number maychange.

Settlement.

Settlement between the operator of some or all of the steps of themethod of FIG. 2 (consisting of FIGS. 2A and 2B) and the cellulartelephone operators who pay on behalf of the subscriber is made as shownaccording to FIG. 3.

Referring now to FIG. 3, the operator of some or all of the method ofFIG. 2 registers 310 to the clearinghouses, MACH or Syniverse, as aroaming service provider if such operator has not done so as describedabove. Any charges in entries received (as records) as described aboveare converted 312 by the clearinghouse or by the operator of some or allof the method of FIG. 2 to SDRs from the local currency of the operator.SDRs are a conventional basket of currencies.

The operator's clearinghouse will aggregate 314 105% of the SDRs foreach operator and at the end of a period, such as a certain day of themonth, will offset credits and debits in each operator's account andsettle all creditors and debtors according to what is owed, using theextra 5% for change in currency conversion differences 316. Theclearinghouse then credits or debits the operators' accounts in theirlocal currency 318.

Registration.

In one embodiment, the user may associate their cell phone with a useraccount at a merchant trusted by the cell phone payment processor whoperforms some or all of the method of FIG. 2. After a first time, inwhich the process above may be followed, even for a pretend charge madeat the time of registration, the user can then make subsequent chargesfrom that same account at the merchant using their cell phone accountswithout having to repeat the entire process described above. In thisembodiment, after the user completes authentication process at a firsttime via a first charge or test as described above, at a second time,after the first time, that the user makes a charge from the samemerchant, the method does not make another attempt to validate the uservia the challenge and response, at least for a period of time after thefirst challenge and response has been properly performed. The benefitsof the convenience of such an approach may be worth the lower level ofsecurity that occurs from not validating that the user has the phonewhen the merchant registers the user and therefore, authenticates theuser via the merchant's own procedures (e.g. via a username andpassword) and the typical charges at such a merchant are small. Oneembodiment of this approach is described in FIG. 4.

There are different ways of handling the registration and purchases ofproducts and services. In one embodiment, when the merchant registersthe user, the merchant allows the user to specify their cell phonenumber, and the merchant initiates a $0 charge as described above inorder to allow the user to be set up with the cell phone paymentprocessor. In another embodiment, the merchant will not make any chargevia the cell phone payment processor until the user purchases a productor service. In whichever arrangement is used, the first time themerchant makes the $0 or the real charge, the user will receive, via atext or other message sent to the user's mobile device, the challengephrase from the cell phone payment processor. Subsequent to that, atleast for a period of time or number of charges or other thresholdamount, charges from the same registered user identifier will notrequire sending of a challenge phrase or the challenge phrase to beresponded to by the user.

FIG. 4 is a method of processing payments using a cellular telephoneaccount for a registered user of a web site according to one embodimentof the present invention.

The cell phone payment processor registers as described above in step210 as described above if it has not already done so as described above.

The user signs in (or registers), and optionally adds products andservices to an online shopping cart, and checks out as described aboveor merely completes a registration process. The merchant provides thecellular payment processor with the amount (which may be zero if noproducts or services were added, but the user is instead just checkingout), an identifier of the merchant (or such identifier may be inferredbased on the referring URL or using other conventional techniques) alongwith an identifier of the user that the merchant will use to identifythe user to the cellular payment processor and other information asdescribed above 410. The identifier of the user may be the useridentifier used to identify the user to that merchant or it may be aunique alias that the merchant can assign to the user or calculate byhashing the user identifier the user uses to identify himself or herselfto the merchant to produce a unique result, such as by a substitutioncypher or using other conventional techniques.

The user is authenticated, and payment is processed 412 as describedabove with respect to FIG. 2. If the charge is 0, however, no charge isactually made to the user's cell phone, nor is a credit provided to themerchant, though a $0 credit may be provided to the merchant to indicatethat the authentication process is complete. In addition, the cellularpayment processor also associates 414 the merchant identifier andidentifier of the user with the cellular telephone number and IMSIreceived as described above. This information will allow detection ofwhether the user has closed his or her cell phone account or changedtelephone numbers, which would impact the ability to charge the samecell phone account to receive payment from that subscriber by chargingthe same telephone number as described above.

At a later time, the user may log into the same user account at the samemerchant, adds additional goods and services to an online shopping cartthat may be different or the same as the goods and services previouslypaid for by that user, as described above 416. The merchant will againsend to the cell phone payment processor the merchant identifier (orinformation received by the cell phone payment processor will allow thecell phone payment processor to identify the merchant), the amount ofthe charge, and the user identifier or alternate user identifier for theuser. The user identifier or alternate user identifier may be the sameone sent previously for that user, or may be an identifier thatotherwise allows the cell phone payment processor to identify the useras the same user.

The above technique may be used, for example, for a one click shoppingexperience, in which the user does not separately check out, but merelyclicks a button to instantly purchase the item. This technique may alsobe used for recurring charges, such as subscriptions.

If the charge meets one or more criteria, such as the charge is under athreshold limit and the merchant is trusted, and an amount of time sincethe prior charge from that same user for the same merchant does notexceed a threshold amount of time 418, the method continues at step 420,and otherwise 418, the method continues at step 412.

At step 420, the telephone number is used to identify the user's IMSIfrom a roaming clearinghouse as described above with reference to FIG.2A, and that IMSI received is compared to the one previously stored forthe combination of merchant identifier and user identifier received asdescribed above.

If the IMSI requested and received from the clearinghouse does not matchthe one stored 424, the method continues at step 412. In this case, thesteps that initiate the charge to the user's cell phone, the credit tothe merchant, and the performance of the goods or services action, willthus not be performed in response to the most recent receipt of theinformation from the merchant as described above.

In one embodiment, if the IMSI requested and received from theclearinghouse does not match the one stored, the transaction is refusedinstead of continuing at step 412. In this embodiment, the merchant mayelect to reregister the user, for example via a $0 charge, as describedabove, or may provide the actual charge with an additional referrerfield that indicates that the user is being reregistered. In oneembodiment, instead of providing such information via referrerinformation, a separate API is used to allow the merchant to pass theinformation that would be in the referrer information to the cell phonepayment processor without referring the user to a web site operated bythe cell phone payment processor.

If the IMSI requested and received from the clearinghouse does match theone stored 424, the transaction continues at step 264. Thus, payment isprocessed, (the user's cell phone account is charged and the merchantreceives a credit), the merchant is informed of a successful payment,and the goods or services action is performed by the merchant, withoutthe challenge and response or other checking to see that the user hasthe phone in one embodiment, and in one embodiment, may even proceedwithout regard to creditworthiness or the balance in the account, thoughin another embodiment, instead of continuing at step 264, the methodcontinues at step 238 if the prior payment was from a prepaid account.The account type may be stored as part of step 414 in this embodimentand the determination as to whether the account is a prepaid account mayuse such stored account type.

Other Ways of Charging a User's Cell Phone Account.

In one embodiment, if the charge cannot be made to the user's cell phoneaccount via roaming charges, in one embodiment, one or more premium SMScharges may be assessed to the user's cell phone account, with the totalof the charge for the one or more premium SMS messages being equal to orapproximately equal to the total amount of the charge that would havebeen made to the user's account as described above. This allows usersfor whom roaming charges cannot be assessed to use the system and methoddescribed above.

Merchant does not Support Cell Phone Payment.

The merchant may not support payment by cellular telephone. In suchcase, alternative arrangements to cellular telephone payment processingmay be employed.

There are several embodiments of the present invention that address thisissue. The embodiments share a common theme, in that the user uses hiscell phone to fund or pay for a debit or credit card, the card number issupplied to the user (along with an expiration date and security code,e.g. CCID), and the user supplies this information to the merchant topay for the goods or services ordered from the merchant, such as anonline merchant in a conventional manner. The amount transferred to thecard may be the amount charged to the card by a merchant, and anadditional fee may be charged for the transfer. The amount transferredto the card may be an amount that can be independent of any merchantcharge, such as an amount specified by the user. Because the card is aconventional credit card or debit card, no direct relationship betweenthe cell phone payment processor and the merchant needs to be arranged,though the conventional indirect relationships through a transactionnetwork such as Visa or Mastercard are utilized

In this case, the cell phone payment processor becomes the merchant andsells credit services or prepaid or on demand debit cards or fundsexisting debit cards. The user then takes the card information for thecard to a second merchant and uses the card to purchase goods and/orservices from the second merchant.

In each of FIGS. 5A and 5B, the cell phone payment processor registersas described above in step 210.

Funding in an Amount of Each Charge.

Referring now to FIG. 5A, a method of providing and using a debit orcredit card account funded by a cellular telephone account upon chargesmade by a merchant is shown according to one embodiment of the presentinvention. In this embodiment, any amount charged to the card initiatesa transfer from the user's cell phone account to the card as describedabove to fund the charge. The method operates with either a prepaid orpostpaid cell phone account.

Card numbers are obtained from an transaction network and registeredthrough the transaction network and a card processor to the cell phonepayment processor. In one embodiment, to register the card numbers, aset of card numbers are requested and received 510 from a transactionnetwork, such as Visa or Mastercard, optionally via an issuing bank ifthe payment processor is not operating in this capacity. The cardnumbers received are registered 512 to a credit and/or debit cardprocessor, referred to as a “card processor”, by the transactionnetwork. The card numbers are registered 514 to the cell phone paymentprocessor by the card processor. In one embodiment, the recipients ofthe card numbers of step 510 are both the card processor and the cellphone payment processor, though the cell phone payment processor mayreceive the numbers from the card processor after it receives thenumbers from the transaction network.

The subscriber requests 516 a card number via an SMS short code or aUSSD code or a message from a mobile application installed or running onthe subscriber's mobile device sent to the cell phone payment processor(and the message received by the cell phone payment processor willinclude the sender's phone number) or via a web site of the cell phonepayment processor or other related party. In the case of the web site,the subscriber may also identify his or her phone number, and achallenge phrase may be sent to the user's phone (e.g. via SMS or USSDmessage) for the user to enter to the web site in order to validate therequest (unless the user logs on using a username and password, in oneembodiment, because the user authenticates himself or herself via thelog on). In this case, the amount of the purchase may not be specifiedas part of the request. Messages may be sent via SMS or USSD.

The cell phone payment processor receives the cell number and(optionally, if it validates it as described above) associates 518 oneof the card numbers it receives as described above, and optionally thedate and time, with cell phone number and the IMSI corresponding to thereceived phone number, which it requests from the clearinghouse usingthe cell phone number as described above as part of step 518. Cardinformation, such as card number, expiration date and a security code,each received as part of step 510 (or generated and stored, associatedwith the cell phone number, and optionally provided to the cardprocessor and/or transaction network as part of step 518) are providedto the subscriber as part of step 518. The card may be a credit card ora debit card.

The subscriber purchases goods and/or services online or in a store andprovides 520 some or all of the card information to the merchant, whosends 522 to the merchant's payment processor, for example, over anetwork, some or all of the information received, and an amount to becharged. The merchant's payment processor forwards the request to thetransaction network 524 and the transaction network forwards 540 some orall of the information in the request to the cell phone paymentprocessor's card processor. In another embodiment, at steps 524-540, themerchant's payment processor sends the card number to the transactionnetwork, who identifies the cell phone payment processor's cardprocessor to the merchant's payment processor, and the merchant'spayment processor sends some or all of the request directly to the cellphone payment processor's card processor.

The card processor sends some or all of the request to the cell phonepayment processor 542.

The cell phone payment processor receives the request and uses theaccount number to compare the other information, such as expiration datereceived with the request against that stored at step 542. If the otherinformation does not match or the card number cannot be found or is notassociated with a cell number 544, the transaction is refused at step552, described in more detail below.

In one embodiment, the user only has a limited amount of time fromissuance to use the card. In such embodiment, if the card was issuedless than a threshold amount of time ago 544, the cell phone paymentprocessor attempts 546 to authorize (and make) the charges to thesubscriber's cell phone as described above with reference to some or allof steps 220-240 and 260-270, with the following differences. Instead ofstep 246, step 552 is used: that is, if the attempt is unsuccessful 548,for example, because the subscriber's prepaid balance is insufficient,the cell phone payment processor refuses the transaction to the cellphone payment processor card processor 542. The card processor willcommunicate the refusal to the merchant payment processor, optionallyvia the transaction network, and the merchant payment processor willinform the merchant, who will refuse to perform the goods or servicesaction.

In one embodiment, the challenge and response check is not performed aspart of step 546, because it is performed at the time the user requeststhe card. In another embodiment, the challenge and response check isperformed if a threshold amount of time has elapsed since the userrequested the card but is not performed otherwise. In anotherembodiment, such check is always performed.

In one embodiment, the fraud check may not be performed as part of step546. In one embodiment, the fraud check is performed using the name ofthe merchant and a database of countries in which that merchantoperates, with the fraud score being calculated based on the country inwhich the merchant operates that would produce the most favorable score,least favorable score or using an average of each score for each countryin which the merchant operates. Merchants not listed in the database,may generate a high fraud score in one embodiment. The fraud check mayomit the country of the destination of any goods or services as afactor, because it is not known, or it may be used if made part of therequest.

If the card was issued more than the threshold amount of time ago, inone embodiment, the transaction is refused at step 552, described inmore detail below. In another embodiment, no such requirement to use thecard within a threshold amount of time is required, and step 544 doesnot include such a test.

In one embodiment, as part of step 546, if the attempt to charge theuser's cell phone account is unsuccessful due to an insufficient prepaidbalance, the user may be instructed (via the web site he or she may beusing or via an SMS text message) that the prepaid balance isinsufficient and requested to add additional funds to the cell phoneaccount. A short wait period may be performed, such as ten minutes andthen another attempt is made. After the failure of the second attempt,the attempt is considered unsuccessful at step 248. If the secondattempt succeeds, the attempt is considered to be successful at step548.

If the attempt is successful 548, either because the challenge andresponse check and the fraud check were both successfully passed asdescribed above, and either sufficient funds were available in thesubscriber's prepaid account or the subscriber has a postpaid account ingood standing and the charge will not exceed any credit limit asdescribed above, the charge is authorized and the merchant is soinformed, via the card processor and payment processor, optionally viathe transaction network, and the merchant performs the goods or servicesaction for the goods and services corresponding to the transaction 550.

In one embodiment, a merchant identifier is part of the request and iscommunicated from the merchant to the cell phone payment processor withother information as described above. In one embodiment, the merchantidentifier, and, if not already associated, the phone number and IMSI isassociated with the credit card number as part of step 550. In thisembodiment, if the card was not recently issued 544, if it is being usedby a merchant for which it was associated as part of step 550 when itwas previously used, and the merchant is a trusted merchant (e.g. onethe cell phone payment processor believes will have a low incidence offraud, for example, because the charges are usually low and thecustomers of that merchant are usually registered 554, the IMSI isrequested 556 from the clearinghouse using the phone number associatedwith the card. If the IMSI for the phone number associated with the cardis the same as that previously associated with the card 558, the cellphone account is charged as described above using some or all of steps220-240 and 260-272. Thus, a user who does not use the card right awaymay nevertheless be allowed to continue using the card. The otherinformation compared in step 542 is still required to pass the test asdescribed above, or step 552 will still follow step 542 in this case.

Funding by User Request.

FIG. 5B is a flowchart illustrating a method of paying for a purchase ofgoods and/or services, such as those made via the Internet by a creditor debit card that is funded through a cell phone account by userspecification according to one embodiment of the present invention. Inthis embodiment, the user transfers a requested amount from his or hercell phone account to a debit card. An additional fee may be charged orthe amount added to the card may be less than the amount deducted fromthe cell phone account by the amount of a fee. The debit card may thenbe used in a conventional fashion to purchase the goods and services.

Referring now to FIG. 5B, steps 510-514 operate the same as the stepswith the same number in FIG. 5A, except that prepaid debit card numbersare used instead of debit card or credit card numbers.

The user uses a web site or an SMS text message or USSD message torequest a card number, and an amount to be added to the card, orspecifies a card number to which an increase is desired, along with theamount of the increase 517. In one embodiment, the amount also includesa fee for the transfer that will not be added to the card but will bededucted from the subscriber's cell phone account and in anotherembodiment, such a charge is added to the user-specified amount. Instill another embodiment, the user specifies the amount to be charged tothe cell phone account, and the amount credited the card is reduced by afee. In one embodiment, no fees are assessed for the transfer.

The cell phone payment processor receives the information provided instep 517 and attempts to charge the user's cell phone account asdescribed above with respect to some or all of steps 220-240 and260-272, however step 246 is replaced by step 537 or 539 as described inmore detail below. The amounts charged and credited are those describedabove

If the attempt to charge the user's cell phone account is successful(i.e. the subscriber optionally correctly responds to the challengephrase and there is no fraud detected, and either the prepaid balance issufficient or the subscriber's postpaid account is in good standing andany applicable credit limits have not been exceeded) 532, one of theabove amounts is loaded onto the card (which includes loading the amountonto a stored value card, or loading the amount onto an accountcorresponding to the card) 534 and the user may use the card in aconventional fashion as described below.

If the attempt to charge the user's cell phone account is unsuccessful532, in one embodiment, the user's request is refused, for example, byso indicating, using the manner the user used to make the request (e.g.via text message to the web site), or in a different manner 537, and theuser may make another attempt at a different time, starting at step 517,or, if there are funds on an existing card, may perform step 520.

In one embodiment, instead of refusing the user at step 537, the user isnotified that their prepaid balance is insufficient or their creditstanding is not sufficient and the user is given time to correct thesituation, for example, by paying their bill or adding more funds totheir cell phone account 539. A second attempt is made at a later time,and the method continues at step 530, however, in one embodiment, if thesecond attempt is unsuccessful at step 532, step 537 is performed.

The user purchases goods and/or services at an online or other merchantand the transaction is processed as described above with respect tosteps 520-524 and 540-542. (In the case of a stored value card, insteadof steps 522, 524, 540 and 542, the value is deducted from the card ifsufficient funds are stored on the card and a conventional securitycheck is successful, or the transaction is refused otherwise) and themethod continues at step 520 or 517.

If sufficient funds for the transaction are on the card or in theaccount corresponding to the card 545, payment is authorized to themerchant in the amount specified by the merchant in the request, lessany fee, and the amount is deducted from the card or the card account547. The fee may be in addition to the amount and so the total isdeducted from the card or the card account The method may continue atsteps 520 or 517.

If sufficient funds are not on the card or in the account correspondingto the card 545, the transaction may be refused 562 and the methodcontinues at step 517 or 520. In one embodiment, step 562 includessending the user a text message reminding him or her to add funds to thecard.

Although one user and one merchant are described above, the system andmethod of the present invention may be applied to multiple users andeach user may use multiple merchants, some of which are shared bydifferent users. All of the users employ multiple cell phone operators,some or all of which are shared by multiple users, and some or all usersusing different cell phone operators may use the same cell phone paymentprocessor.

System.

Referring now to FIG. 6, a system for paying an online merchant with acell phone account is shown according to one embodiment of the presentinvention.

Communication interface 620 is a conventional communication interfacerunning conventional communications protocols such as TCP/IP, Ethernet,and other conventional communications protocols. All communication intosystem 600, which includes the elements numbered 620 or above, is madevia communication interface 620. Communication interface 620 is coupledto a network 618, such as an Ethernet, the Internet, or both, via atleast one input/output.

The operator of at least some of system 600 is the cell phone paymentprocessor, and such cell phone payment processor arranges withconventional clearinghouses to pretend to be or to be a conventionalroaming services provider as described above.

User Purchases Products or Services and Checks Out.

Different cell phone subscribers as described above purchase productsand services using user systems 602, which may be conventional computersystems, each running a browser, including mobile devices for whichnetwork services are supplied by cell phone operators (also referred toas cell phone service providers), from merchants via merchant systems606, which may include conventional web servers running one or more webretailer applications to allow a user to purchase products or services,which may be modified as described herein.

When the user uses the above systems to check out, the merchant system606 may direct the user's browser to a user interface supplied by userinterface manager 622, which asks the user for his or her phone number,if the user selects payment by cell phone as the payment method asdescribed above. As noted, the merchant system 606 may be the entitythat requests the user's phone number and provides such information touser interface manager 622 via a conventional API it provides.

User interface manager 622 builds the phone number and other referrerinformation received with the phone number as described above (or suchinformation may be supplied to user interface manager 622 via the API)into a payment record and provides the payment record to challengeresponse manager 624.

Challenge User and Check Response.

When challenge response manager 624 receives the payment record, itprovides a challenge phrase to the user's cell phone using the cellnumber in the payment record as described above. User interface manager622 provides a user interface to the user to enter the challenge phraseand receives it from the user via the Internet. Alternately, themerchant may request the challenge phrase and provide it to userinterface manager 622 via the API. When user interface manager 622receives the challenge phrase, it provides it to challenge responsemanager 624, which compares the challenge phrase received with the oneit generated. If the two are different, it may signal user interfacemanager 622 to request it again until a threshold number of attemptshave been made and failed, at which point, it provides the paymentrecord to user interface manager 622 with an indication that thechallenge phrase was not entered correctly. If the challenge phrasesmatch, challenge response manager 624 provides the payment record touser interface manager 622 and an indication that the challenge phrasewas entered correctly. In one embodiment, challenge response managersets a timer when it provides the challenge phrase, and if the timerelapses before the phrase is received, challenge response manager 624indicates to user interface manager that the challenge phrase did notmatch.

If it receives an indication that the challenge phrase was not enteredcorrectly, user interface manager 622 indicates to the user that thechallenge phrase was not entered correctly, and may then redirect theuser's browser to an error page of the merchant system 606, and themerchant will not perform the goods or services action, the subscriber'scell phone account will not be charged and the merchant account will notbe credited as a result. The redirect may include a merchant-issuedtransaction identifier received with the referrer information that themerchant can use to cancel the transaction or allow the user to use adifferent payment method or another attempt to pay by cell phone.

Returning Registered Users.

In one embodiment, the information communicated from the merchant viathe referrer information or API may contain the identifier of themerchant and the registered username the user uses to log in at themerchant or the or an alternate username that is not the username but isan identifier unique to the merchant that will always be substituted bymerchant system 606 in place of the username to identify the user tosystem 600 after the user logs in to the merchant system 606 using theuser's username as described above. Such information will be made partof the payment record when received by user interface manager 622. Themerchant system 606 may also provide to user interface manager 622 a $0charge at the time of registration or another indication that thetransaction is for purposes of registration as described above.

When challenge response manager 624 receives the payment record, itchecks for a merchant identifier and a username or alternate username.If those two fields are found, it checks a username table for entrieswith the same phone number, merchant identifier and username oralternate username in a registered user table in database 630. If itdoes not find these items, challenge response manager 624 challenges theuser and receives the response as described herein, and if the userprovides the correct response, challenge response manager 624 operatesas described above and builds an entry containing them in the usernametable and adds the current date and time as a timestamp.

As noted below, account information retriever 626 retrieves the accountinformation described above, including the IMSI corresponding to thetelephone number in the payment record. In one embodiment, such accountinformation is retrieved prior to user interface manager 622 providingthe payment record to challenge response manager 624, and challengeresponse manager adds the IMSI to the username table, associated withthe username or alternate username and merchant name. In one embodiment,account information retriever receives a list of country codes and thecellular telephone service providers that service telephones withnumbers having that country code, as well as an estimate or actual orderof market share within that country code, and account informationretriever 626 attempts to retrieve the account information from suchproviders in order or approximate order of the market share as describedabove.

If, at a subsequent time, it locates in the registered user table indatabase 630 the combination of merchant identifier, username oralternate username and phone number in a subsequent payment record, ifthe timestamp is not less than the current date and time by more than athreshold amount, challenge response manager 624 does not provide thechallenge phrase or receive a response. Instead, challenge responsemanager 624 indicates that the user entered the challenge phrasecorrectly, in spite of the fact that the user did not do so because theywere not requested to do so. In one embodiment, challenge responsemanager 624 also checks the IMSI in the payment record (which isretrieved by account information receiver 626 as described above) withthe IMSI associated with the merchant identifier and username oralternate username in the username table, and does not provide thechallenge phrase but instead indicates to user interface manager 622that the user entered the challenge phrase correctly if a) the merchantidentifier and username or alternate username in the payment record islocated in the username table, b) the difference between the currenttime and the timestamp is less than a threshold amount of time, and c)the IMSI in the username table is the same as the IMSI in the paymentrecord. Thus, at the time of a second request received from a merchantfor payment via a cell phone account, the system will operate to chargethe user's cell phone account, credit the merchant and initiate themerchant performing the goods or services action without verifying thatthe user has possession of the telephone corresponding to the telephonenumber it receives when a user has previously provided evidence of suchpossession, as long as the IMSI corresponding to the phone number is thesame as it was at the time of a prior request from that merchant forpayment or registration via the same cell phone account.

If the merchant name, username or alternate username, and phone numberin the payment record match a row in the registered user table indatabase 630, but the timestamp is older than the current date and timeby more than a threshold amount, or the IMSI in the payment record isdifferent from the associated with the merchant identifier and usernameor alternate username in the username table, challenge response manager624 causes the challenge phrase to be sent and compares the any responsewith the challenge phrase, and responds as described above. However, ifthe user enters the challenge phrase correctly, challenge responsemanager 624 updates the timestamp in the corresponding entry in theregistered user table in database 630.

Retrieve Account Information from Clearinghouse.

Simultaneously with the challenge phrase being sent, or around thattime, user interface manager 622 provides the payment record to accountinformation receiver 626, which retrieves the information describedabove from the computer system of the clearinghouse 604 as describedabove and adds it to the payment record. Account information receiver626 provides such updated payment record to user interface manager 622.

Check for Fraud, Bad Account Status, and Chargebacks.

If user interface manager 622 receives the indication that the challengephrase was entered correctly, user interface manager 622 adds the IPaddress of the user to the payment record and provides the updatedpayment record to fraud manager 628.

When it receives the updated payment record, fraud manager 628 performsthe fraud check, status check and chargeback check (checking thechargeback table in database 630 described in more detail below, for theuser's IMSI) as described above. In one embodiment, to perform the fraudcheck, fraud manager 628 locates the country corresponding to the IPaddress in a country/IP address table stored in database 630. Fraudmanager 628 uses the county of the merchant and the country in whichgoods are being shipped that was received in the referrer informationand is stored in the payment record, and uses the country in which thecell phone last operated that was retrieved from the clearinghouse andstored in the payment record to calculate a fraud score as describedabove.

If the fraud score is on one side of a threshold, the account status isbad (suspended or disabled) or the number of applicable chargebacksduring a period of time exceeds a threshold for the merchant (thethreshold for each merchant is stored in the merchant table of database630, with a default value of two per year if no different threshold andperiod is specified by the merchant) and chargebacks are storedassociated with the IMSI as described herein) the transaction isconsidered fraudulent or suspicious, and so fraud manager 628 soindicates, and provides the payment record, to user interface manager622. In response, user interface manager 622 refers the user back to anerror page of the merchant system 606 or indicates to the merchant viathe API using the transaction identifier as described above. Themerchant can then refuse to perform the goods or services action andtake other suitable measures, the subscriber's cell phone account willnot be charged and the merchant's account will not be credited.

If the fraud score is on the other side of the threshold, the accountstatus is not suspended or disabled and the number of chargebacks doesnot exceed the threshold, fraud manager 628 may log, in a fraud table indatabase 630, the different countries and time of day and a uniquetransaction identifier that may be assigned and added to the paymentrecord by user interface manager 622 when it creates the payment record,to allow the fraud model to be refined based on the payment histories ofthe transactions. Fraud manager 628 additionally so indicates that fraudis not detected, the account status is not suspended or disabled and thenumber of chargebacks does not exceed the threshold (and provides thepayment record) to user interface manager 622.

Determine Prepaid/Postpaid Type of Account.

When it receives this indication of no detected fraud, the accountstatus is not suspended or disabled and the number of chargebacks doesnot exceed the threshold, user interface manager 622 provides thepayment record to prepaid determination manager 632. When it receivesthe payment record, prepaid determination manager 632 determines whetherthe user's account is a prepaid account or a postpaid account asdescribed above. To make this determination, prepaid determinationmanager 632 uses the operator identifier stored in the payment record tolocate the contact information instructions for that operator in theoperator table of database 630 and then contacts the operator platformor platforms 608 or clearinghouse system 604 according to the contactinformation, performs the instructions, and interprets the resultsaccording to the interpretation information for that operator in theoperator table of database 630 as described above. Prepaid determinationmanager 632 stores an indication as to whether the subscriber is prepaidor postpaid in the payment record and provides the payment record touser interface manager 622. The operator platform 608 and clearinghousesystem 604 are conventional computer systems, such as web servers.

When it receives the payment record, user interface manager 622 providesthe payment record to balance sufficiency manager 634 if the account isindicated in the payment record as being prepaid, and to creditworthymanager 636 otherwise.

Check Prepaid Balance.

When balance sufficiency manager 634 receives the payment record, ituses the instructions for retrieving the prepaid balance for theoperator in the payment record that are stored in the operator table ofdatabase 630 to contact the appropriate operator platform or platforms608 or clearinghouse system 604 and retrieves the prepaid balance usingthe phone number in the payment record. Balance sufficiency manager 634subtracts any minimum amount that is indicated in the operator table ofdatabase 630 and balance sufficiency manager 634 indicates to userinterface manager 622 whether the remainder is greater than or equal tothe amount of the charge in the payment record (plus any extra fees) andmay store the excess in the payment record. Balance sufficiency manager634 provides the payment record and indicates to user interface manager622 whether the remainder is greater than or equal to the remainder, andmay also reserve or place a hold at the operator platform 608 on theamount to be charged the cell phone account in the operator platform orwith the clearinghouse. Balance sufficiency manager 634 stores in thepayment record the amount of the hold or reservation.

Check Creditworthiness.

When it receives the payment record, creditworthy manager 636 comparesthe amount in the payment record to a credit limit, either a creditlimit that applies to all operators or one that applies to the operatorin the payment record in the operator table in database 630 and if thecredit limit is exceeded by the amount (or other conditions in theoperator table or elsewhere in the database 630 are not met, e.g. thatit is not on a blacklist of phone numbers, etc.), then creditworthymanager 636 provides the payment record and so indicates to userinterface manager 622.

If the credit limit is not exceeded and other conditions are met,creditworthy manager 636 then uses the instructions stored in theoperator table of database 630 for the operator corresponding to thepayment record to determine the location of the operator platform 608 orclearinghouse system 604, the method of identifying the creditworthinessof the account and instructions for interpreting the results, and thenuses such information and the phone number in the payment record toidentify whether the account is creditworthy as described above.Creditworthy manager 636 provides the payment record and suchinformation to user interface manager 622.

Insufficient Balance/not Creditworthy.

In one embodiment, either balance sufficiency manager 634 orcreditworthy manager 636 stores an indication as to whether the issuewas an insufficient balance or the creditworthiness of the account intothe payment record and provides the payment record to user interfacemanager 622 as the signal as described above.

If it receives an indication that the prepaid balance is insufficient orthat the postpaid account is not creditworthy, user interface manager622 so indicates to the user and then redirects the user to an errorpage on the merchant system 606, with referrer information including themerchant's transaction number in the payment record, or to the merchantsystem via the API as described above, and user interface manager 622 orthe merchant system 606 may suggest to the user suitable correctivemeasures, such as topping up the account by the difference stored in thepayment record.

Prepaid Balance Sufficient or Postpaid Account is Creditworthy.

If it receives an indication that the prepaid balance is sufficient orthe postpaid account is creditworthy, user interface manager 622provides the payment record to settlement manager 638. When it receivesthe payment record, settlement manager 638 builds the information fromthe payment record into an entry as described above and provides theentries as records as described above to clearinghouse system 604, whichprocesses them as described above. Settlement manager 638 commits orreleases the hold as required. In addition, settlement manager 638 alsobuilds and stores in an operator accounting table in database 630 a rowcorresponding to the transaction, including the current date and time,operator identifier and amount, and builds and stores in a merchantaccounting table in database 630 a row that contains the merchantidentifier, date and time and amount. Other conventional accountingsteps pertaining to settlement and described herein may also beperformed by settlement manager 638, including clearinghouse system 604providing the tap records for an operator to the operator platform 608,and as a result, the operator platform 608 charges each user's accountin the manner of a roaming service charge.

Settlement manager 638 may assign a transaction identifier, and storesit in both such rows and into the payment record, and provides thepayment record to user interface manager 622 with an indication that thetransaction is complete. User interface manager 622 provides thetransaction identifier, encrypted and signed, via the API, or redirectsthe user back to the merchant site, optionally with referrer informationincluding the merchant transaction number and the assigned transactionidentifier, which user interface manager 622 encrypts and signs. Whenthe merchant system 606 receives the signed transaction identifier, itauthenticates the signature, and if authentic, causes the goods orservices action to be performed, such as by displaying a shipping orderto a shipping department, or indicating to a service provider to providethe service.

Less Verification for Repeat Transactions.

In one embodiment, settlement manager 638 timestamps with the currentdate and time and stores some or all of the payment record into a paidtransactions table in database 630.

At a later time, after the same user initiates another transaction withthe same merchant or a different merchant, user interface manager 622may proceed as described herein. However, if the amount is under athreshold amount, and the same telephone number is received for atransaction as was used for a prior transaction in the paid transactionstable, and the IMSI from the most recent payment record stored in thepaid transactions table having the same phone number matches the currentIMSI retrieved for that phone number and stored in the payment recordfor the transaction being processed, and the timestamp of the mostrecent record stored in the paid transactions table is less than athreshold amount of time from the current time retrieved by userinterface manager 622, and if the merchant is trusted, (or fewer thanthe above conditions are satisfied) user interface manager 622 may add afield to the payment record indicating the payment record was unverifiedand provide the payment record to settlement manager 638 withoutproviding the payment record to balance sufficiency manager 634 orcreditworthy manager 636 so that the payment is processed without regardto balance sufficiency or creditworthiness as described above withreference to FIG. 4 above.

In one embodiment, only a limited number of transactions for asubscriber from the last transaction in which balance sufficiency orcreditworthiness was checked for that subscriber will be processed inthis manner, at which point the balance sufficiency or creditworthinesswill be checked as described above. In one embodiment, only a limitednumber of transactions from a subscriber within a time period (e.g. onemonth or a typical billing cycle) will be processed without checking forcreditworthiness or balance sufficiency, and if the limited number isexceeded by a subscriber, user interface manager 622 checks thattransaction and all subsequent transactions during the period from thatsubscriber for balance sufficiency or creditworthiness as describedabove.

Layaway.

In one embodiment, if the prepaid balance is insufficient or the user isnot considered creditworthy because the user's account is not in goodstanding, user interface manager 622 will ask the user via the web ortheir mobile device as described above if they would like time tocorrect the situation. In one embodiment, as described above, the userneed not respond for the following actions to be taken, and in anotherembodiment, a user indication as to whether to proceed is requested andreceived by user interface manager 622. Either automatically, or if theuser so indicates, user interface manager 622 provides the paymentrecord to layaway manager 640 and may inform merchant system 606 toplace the transaction on hold pending payment, either via the API or byopening a session with the merchant system that identifies thetransaction on hold using the merchant transaction identifier in thepayment record. The merchant system 606 may respond by holding theuser's shopping cart open for a longer period of time than it otherwisewould, but does not perform the goods or services action.

Alternatively, the merchant system 606 may so inform the user, havingreceived an indication that such an option is available via userinterface manager 622 via the API, and if the user respondsaffirmatively, the merchant system 606, so informs user interfacemanager 622 via the API, and user interface manager 622 provides thepayment record to layaway manager 640.

In one embodiment, layaway manager 640 assigns a transaction identifier(which may be the merchant name and its identifier) and an expirationdate and time to the transaction and stores the identifier, the currentdate and time, and the payment record in a layaway table in database630. The expiration date and time optionally is a function of theindication of the issue (creditworthiness or insufficient balance)stored with the payment record as described above, with creditworthinessissues having a longer date and time from the current date and time thanthose with an insufficient prepaid balance, in one embodiment.

Layaway payment manager 642 periodically scans the layaway table forexpiration dates and times that are prior to the current date and time,i.e. expired. For any that it finds expired, layaway payment manager 642retrieves the payment record, increments a counter that was initializedto zero when the payment record was built, provides the payment recordto user interface manager 622 and deletes the corresponding row in thelayaway table in database 630.

When it receives the payment record from layaway manager 642, userinterface manager 622 again sends the payment record to prepaiddetermination manager 632, and processing then occurs from that point onas described above. In one embodiment, user interface manager 622provides the payment record to balance sufficiency manager 634 orcreditworthiness manager 636 based on the type of account stored in thepayment record instead of providing it to prepaid determination manager632, and processing continues from either of those points as describedabove.

If balance sufficiency manager 634 or creditworthiness manager 636indicates that the prepaid balance remains insufficient or that thepostpaid account is not creditworthy as described above, user interfacemanager 622 checks the counter and compares it to a threshold. If thecounter exceeds the threshold, user interface manager 622 informs theuser, the merchant or both that the prepaid balance was insufficient orthe postpaid account was determined to be not creditworthy and the useris instructed to address such issue and start again, or to selectanother mode of payment (e.g. credit card or check) as described above,but the payment record is not provided to layaway manager 640, andprocessing of the payment record continues as described above.

If the counter does not exceed the threshold, user interface manager 622again provides the payment record to layaway manager 640, whichprocesses it as described above. In one embodiment, user interfacemanager will inform the user, for example via text message or the website, that the prepaid balance remains insufficient or the postpaidaccount remains not in good standing after another attempt and asks ifthe user needs more time to correct the issue. User interface manager622 processes the response as described above.

In one embodiment, user interface manager 622 requests a paymentschedule from the user via the web interface it provides or allows themerchant system 606 to do so, and merchant system 606 communicatespayment schedule information (e.g. the number of equal monthlyinstallments) to user interface manager 622. User interface manager 622adds the payment schedule information to the payment record beforeproviding it to layaway manager 640, which adds the next payment date asthe expiration date. Layaway payment manager 642 retrieves the paymentrecord at the next scheduled payment date (i.e. the expiration date),and provides the payment record to user interface manager 622, whichprovides it to prepaid determination manager 632 as described above andprocessing continues from that point as described above. The amount ofthe charge that will be checked against the balance for sufficiency fora prepaid account by balance sufficiency manager 634, compared againstthe credit limit by creditworthy manager 636, or charged to the user'saccount by settlement manager 638 is the next scheduled payment amount.Settlement manager 638 maintains the amounts paid for the transaction ina layaway table in database 630 and only when the transaction is paid infull does settlement manager 638 provide the payment record to userinterface manager 622 with the indication that the transaction iscomplete. At each monthly payment prior to the last one, settlementmanager 638 updates the amount due and the next scheduled payment andprovides the payment record to layaway manager 640, which assigns thenext scheduled payment date as the expiration date and stores it asdescribed above. If a payment is not completed because the prepaidbalance is insufficient or a postpaid account is not creditworthy,settlement manager 638 proceeds as described above, to cause thenotification of the subscriber to remedy the issue.

Chargebacks.

Chargebacks are transactions initiated by the merchant for a customerreturn with a negative amount. If a negative amount is received by userinterface manager 622, user interface manager 622 passes the paymentrecord to settlement manager instead of providing it to balancesufficiency manager 634 or creditworthy manager 636. Settlement manager638 processes chargebacks in the same manner as described above, but theamounts are negative or otherwise indicated as such, and settlementmanager 638 stores the IMSI, date, time and amount of the chargebackinto a chargeback table in database 630.

On Demand Credit or Debit Card.

As noted above, for merchants who do not provide or receive theinformation described above, a credit or debit card that is funded bythe user's cell phone account may be used instead. The system providescard information to the user for the user to use like any other creditcard or debit card, and processes charges to the user's cell phoneaccount, as will now be described.

Card registration manager 644 requests and receives card numbers fromtransaction network system 614 optionally via card processor system 612and an issuing bank. Transaction network system 614 and card processorsystem 612 are each conventional computer systems including conventionalweb server software. Transaction network system 614 registers the cardnumbers to card processor system 612 and card processor system 612registers the card numbers to cell phone payment processor system 600,each of which includes a conventional computer system including a webserver. Card registration manager 644 stores the card numbers into acard table in database 630.

Transaction network system 614 is operated by a transaction network suchas Visa or Mastercard. Card processor system 612 is operated by acompany that handles credit and/or debit processing for and paymentprocessor system 610

At any time, users may request a card to be issued to them as describedabove. To do so, the user uses user system 602 to communicate with cardissue manager 646, for example via a mobile device or web page asdescribed above. When the user does so, card issue manager 646 requestsand receives the IMSI for the phone number received as described abovefrom account information retriever 626, which retrieves the IMSI andprovides it to card issue manager 646. Card issue manager 646 associateswith the user's cell phone number and the IMSI one of the card numbersin the card table of database 630 that is not already associated with auser's cell phone and provides the card information to the user asdescribed above. In one embodiment, the expiration date and securitycode are generated by card issue manager 646 and stored in the databaseassociated with the card number. In one embodiment, card issue manager646 also associates the current date and time with the card number.

The user then uses user system 602 to purchase goods and/or servicesfrom merchant system 606 using conventional techniques, and checks outusing the card information received as described above. The merchantsystem sends a request for payment, including the card information andthe amount of the charge to payment processor 610, which includes aconventional computer system, and may include a conventional web server.Payment processor 610 either sends the request to transaction networksystem 614, which forwards it to card processor 612 based on theregistered card number, or sends the card number to transaction network614, which identifies to payment processor 610 card processor 612 as theentity to process the transaction, and payment processor 610 sends therequest to card processor 612.

When it receives the request, card processor 612 uses the card number toidentify the cell phone payment processor 600 as the issuing financialinstitution and forwards the request to card charge manager 648. Cardcharge manager 648 uses the card number to check the other informationreceived in the request with the other information stored in the cardtable of database 630 for the card number (expiration date and securitycode), and ensures it matches. If it does not match or the card numberis not located, card charge manager 648 rejects the request by sendingan identifier received with the request to card processor 612, whichsends it to payment processor 610 optionally via the transaction networksystem 614. Payment processor 610 sends the rejection to the merchantsystem 606, and the merchant may allow the user to make other paymentarrangements but does not receive payment and does not perform the goodsor services action as a result of the request.

If the other information matches, card charge manager 648 builds apayment record consisting of the information in the request, includingthe amount being charged by the merchant from the request and the cellphone number and IMSI associated with the card number in the request,and, in one embodiment, checks to see if the card was recently issued.In one embodiment, if the card was not recently issued, card chargemanager 648 so indicates in the payment record. Card charge manager 648also marks the payment record to indicate that responses to the paymentrecord as described below are to be sent to charge card manager 648. Inone embodiment, if the card was not recently issued, card charge manager648 sends the payment record to challenge response manager 624 whichproceeds as described above and provides the indication to card chargemanager 648. If the challenge phrase was entered incorrectly, cardcharge manager 648 may repeat the process to retry up to a number oftimes and if still entered incorrectly, card charge manager 648 rejectsthe request as described above. If it receives the indication that thechallenge phrase was entered correctly, card charge manager 648continues as described below. In another embodiment, if the card was notrecently issued, card charge manager 648 provides the payment record tocard trust manager 650 for processing as described below.

If the card was recently issued or the challenge phrase was enteredcorrectly, card charge manager 648 provides the payment record toaccount information retriever 626 which retrieves the accountinformation as described above, places it into the payment record andprovides the payment record to card charge manager 648. Card chargemanager 648 provides the payment record to prepaid determination manager632, which makes the determination described above, adds the indicationof whether the user's account is prepaid or postpaid to the paymentrecord and provides the payment record to card charge manager 648. Whenit receives the payment record, card charge manager 648 uses theindication of whether the user's account is prepaid or postpaid toprovide the payment record to balance sufficiency manager 634 orcreditworthy manager 636 in the same manner as user interface manager622 described above, balance sufficiency manager 634 or creditworthymanager 636 operate as described above and provide the payment record,including the selected one's respective indication, to card chargemanager 648.

If the indication is that the prepaid balance is insufficient or theaccount is not in good standing, in one embodiment, card charge manager648 provides the payment record to layaway manager 640, which proceedsas described above, to prompt the user to correct the issue and layawaypayment manager 642 will operate as described above and will signal cardcharge manager 648 at the expiration date and time (which may be shorterin this case than it would be if the charge was coming directly frommerchant system 606 as described above) to repeat the process startingwith the account information being retrieved. The number of attempts itmakes may be limited to one. If the attempts fail, or, in anotherembodiment, if the original indication is that the prepaid balance isinsufficient or the account is not in good standing, in one embodimentcard charge manager 648 rejects the charge as described above.

If the indication in the payment record is that the prepaid balance issufficient or the user's account is creditworthy, card charge manager648 provides the payment record to settlement manager 638, which chargesthe user's cell phone account as described above, and uses the cardidentifier as the merchant for accounting purposes as it stores entriesin the database as described above. Card charge manager 648 builds andsends an approval of the charge to card processor 612, which sends it topayment processor 610, optionally via transaction network system 614.Payment processor 610 notifies the merchant system 606, which causes themerchant to perform the goods or services action as described above.

In one embodiment, card charge manager 648 associates with the cardnumber in database 630 the merchant from the request and the IMSIretrieved as described above. In such embodiment, if, at a subsequenttime the card is used, the card is not recently issued, but the merchantin a request is the same as one associated with the card from a priortransaction to that card, and the merchant name matches a merchant froma trusted merchant table in database 630, the request will be processed,optionally without the use of challenge response manager 624 and willinstead be treated as if the challenge phrase was entered correctly. Inanother embodiment, challenge response manager 624 is used as describedabove if the merchant is in the trusted merchant table, but thetransaction will not be refused. If the merchant is not in the trustedmerchant table, the transaction may be refused by card charge manager648, or challenge response manager 624 may be used as described above.In one embodiment, if challenge response manager 624 is not ordinarilyused for a trusted merchant, and in another embodiment, if the card isnot recently issued and challenge response manager 624 is used, cardcharge manager 648 compares the IMSI retrieved by account informationretriever 626 and stored in the payment record with the IMSI associatedwith the card in database 630. If the two IMSIs do not match, eitherchallenge response manager 624 will be used by card charge manager 648as described above or the transaction may be refused by card chargemanager 648 as described above.

Manual Purchase and Reload of Card.

As noted above, in one embodiment, the user may purchase a prepaid debitcard or add value to a previously purchased card.

Purchase or Adding Value to a Prepaid Card.

In such embodiment, a user may purchase, or increase the stored valueon, a prepaid debit card by navigating a browser on the user system 602to a web page provided by, or sending a text message (which includes SMSmessages and USSD messages) to, prepaid sell manager 652. The userincludes the amount desired to add to the card or amount to charge tothe user's cell phone account, the card number if adding funds to anexisting card, and the user's cell phone number if the web page is used(prepaid sell manager 652 will receive the user's phone number as partof the text message if that is used).

If the user is purchasing a new card, prepaid sell manager 652associates one of the card numbers in the card table in database 630. Inone embodiment, debit and credit card numbers are segregated, with eachtype requested and received as described above, and card registrationmanager 644 marks the type of card in the row for that card in the cardtable in database 630. Prepaid sell manager 652 associates a prepaidcards not already associated with a user's cell phone. Prepaid cellmanager 652 may request the user enter a username and password, orinstruct the user to send a USSD message from their mobile device, whichmay be part of the user system 602.

Prepaid sell manager 652 then uses the API to communicate the user'sphone number and the amount the user indicated to add to the card orcharge to their cell account to user interface manager 622 as describedabove, with prepaid sell manager 652 acting as the merchant and using amerchant name. In one embodiment, if the user has authenticated itselfto prepaid sell manager using a username and password, the username oralternate username are provided as part of the API, with a trustedmerchant name to avoid the use of the challenge phrase (or a“supertrusted merchant name” which will cause challenge response manager624 to skip the challenge phrase even for the first use by that user),or they need not be provided and the merchant name is a name that is nottrusted, so that the challenge phrase will be provided as part of theuse of the API as described above. If an error is returned by userinterface manager 622 (for example, because the user did not correctlyenter the challenge phrase, the prepaid balance is insufficient or thepostpaid account is not in good standing, prepaid sell manager 652 soindicates to the user and suggests the user correct the issue and tryagain. Layaway manager 640 and layaway payment manager 642 may performthis function in the manner described above and automatically initiatethe retry as described above. If the charge is made to the user'saccount, user interface manager 622 informs prepaid sell manager 652 asdescribed above, and prepaid sell manager 652 increases by the amount ofthe charge (less any fee) in the row in the card table corresponding tothe card number in database 630 an available balance amount, initializedto zero by card registration manager 644. Prepaid sell manager 652provides the card number to the user (or provides it if the card isbeing newly issued or had a zero balance) and indicates that the amountis available to be used.

Using the Prepaid Card.

The user uses a prepaid card as described above. However, if there is abalance on the card, card charge manager 648 will first use the balanceon the card before attempting to charge the user's cell phone account asdescribed above. In one embodiment, when a prepaid card is purchased,prepaid sell manager 652 may mark the row in the card table in database630 as prohibiting automatic charges, for example, if the user sorequests such status from prepaid sell manager 652 when the card ispurchased or value is added to the card. In such embodiment, card chargemanager 648 will not automatically attempt to charge the user's cellphone account if a charge is received from a merchant that is in excessof the amount of the prepaid value remaining on the card and the rowcorresponding to the card number in the card table in database 630indicates that automatic charges are prohibited. In such case, thecharge will be refused, and the user may be so informed by card chargemanager 648, which instructs the user to add value to the card and tryagain.

In one embodiment, special field is used in the payment record when ondemand or prepaid credit cards are used, which indicates to fraudmanager 628 not to perform the fraud check, or to perform it usingconventional credit or debit card fraud detection techniques. Themerchant name may be copied from the request into the payment record bycard charge manager 648 for use by fraud manager 628.

When the merchant is paid via the on demand credit card or the cellphone account-linked debit card described above, the merchant willperform the goods or services action as described above, and will notperform it in response to submission of the card information if paymentis refused, until payment is received either from such card or anotherform of payment. In one embodiment, a goods or services action does notinclude supplying cell service- or mobile device-related services ormobile device-related products.

Thus, a system and method allows for a user to pay a merchant to performa goods or services action using a cell phone account or a credit ordebit card that is funded by a cell phone account. Funding is performedby charging as if a roaming service had been provided, when in fact nonewas provided for that customer or the roaming service charged was notprovided. A cell phone account is an account that is used to providemobile communication services.

Funding is performed by the user or a merchant explicitly specifying atleast one decimal number containing, at least for some amounts, anamount other than zero to the right of the decimal place. Explicitspecification means the transmission of that number. For example,specifying $0.10. Specifying “one” unit of a limited number of amountsthat is much fewer (e.g. less than half) than all possible amounts, suchas $0.10 is not considered explicit specification in one embodiment. Inone embodiment, “specification of an exact amount” is made using asingle (or very few) requests that can specify any or most amountswithin a range, for example a range exceeding $5.00 or 5 euros from thelowest amount to the highest amount. For example, if one may specify anyeven numbered amount between $0.10 and $10, and optionally add a penny,that is specification of an exact amount, in spite of the fact thatamounts outside the range are not possible and an extra penny must bespecified for odd amounts. In one embodiment, specification of an exactamount does not include sending more than a few separate requests tospecify any permissible amount within a range, or specification systemsthat do not allow specification of at least half the amounts within therange. So, for example, having to send a request for each $1 and each$0.10 is not specification of an exact amount, because the amount of$5.93 requires many request and also does not allow the $0.03 to bespecified at all. Either one of these reasons would disqualify such asystem as being one in which specification of an exact amount is allowedin one embodiment.

In one embodiment, any utility may be used in place of a cell phoneaccount. For example, an electric account may be used.

Although two clearinghouse systems 604, two user systems 602, twomerchant systems 606, two operator platforms 608, two payment processors610, two card processors 612 and two transaction networks 614 are shown,any number of these may be used, and each may operated by entities thatare different from one another (and not controlled by or controlling oneanother) and different from (and not under control of or controlling)the entity operating cell phone payment processor system 600.

Communication with Operators.

In the circumstance in which communication is made with operatorplatform 608 as described above, message formats are received from theoperator and typically communicated using HTTP messages. In some cases,multiple platforms from the same operator may be used to obtain theinformation and provide the charge information described above. In thiscase, a single box behind the operator's firewall may be used to receiveeach message, direct it to the appropriate operator platform based onthe content of the message, and return any response to the source of themessage.

In one embodiment, a user may be directed to send a USSD messagewherever the user is instructed to send a text message. For example, theuser may be directed by challenge response manager 624 via a textmessage to type *24 or #24 on his or her cell phone. The operatorplatform 608 will receive the USSD message and provide an indicationthat such a message was received from the subscriber, along with thesubscriber's phone number, to communication interface 620, which willroute such message to challenge response manager 624. In one embodiment,the indication contains the number that was used, and this number isused to route the indication by communication interface 620.

SUMMARY

There has been described a method of paying for a product or service,including the steps of: at a first time, receiving from a merchant by apayment processor that is a sineroaming roaming services provider, anaccount identifier for a user at that merchant, and a telephone numberof the user as a request for payment to the merchant by the sineroamingroaming services provider; verifying that the user has possession of thetelephone corresponding to the telephone number received; associatingthe telephone number with the account identifier responsive to theverifying that the user has possession of said telephone; at a secondtime, subsequent to the first time, receiving by the payment processoran amount from the merchant for the product or service, other thanroaming or another mobile-related product or service and at least oneselected from the account identifier and the telephone number;responsive to the account identifier or telephone number or bothreceived at second time, determining whether the telephone number wasassociated with the account identifier; generating, to a mobiletelephone account corresponding to the telephone number received, aroaming charge responsive to the amount without verifying that said userhas possession of said telephone between the second time and thegenerating step; causing the merchant to perform a goods or servicesaction without verifying that said user has possession of said telephonebetween the second time and the causing the merchant to perform step;and causing the merchant to be provided funds responsive to the amountwithout verifying that said user has possession of said telephonebetween the second time and the causing the merchant to be providedstep.

The above method may be performed, where at least one selected from thegenerating and both causing steps are responsive to the determiningstep.

The above method may be performed with the additional step ofassociating an identifier of the merchant with at least one selectedfrom the telephone number and the account identifier.

The above method may be performed with the additional steps of, at themerchant, at each of the first time and the second time: receiving auser identifier from the user; converting the user identifier receivedinto the account identifier, the user identifier received from the userbeing different from the account identifier; and providing the accountidentifier to a payment processor.

The above method may be performed when, at the first time, the merchantindicates that the user is being registered.

The above method may be performed with the additional steps of:obtaining a first international mobile subscriber identity coderesponsive to the telephone number received at the first time; obtaininga second international mobile subscriber identity code responsive to thetelephone number received at the second time; and comparing the firstinternational mobile subscriber identity code and the secondinternational mobile subscriber identity code; and where at least oneselected from the generating and both causing steps are responsive tothe comparing step.

The above method may be performed with the additional steps of:obtaining a first international mobile subscriber identity coderesponsive to the telephone number received at the first time; obtaininga second international mobile subscriber identity code responsive to thetelephone number received at the second time; and comparing the firstinternational mobile subscriber identity code and the secondinternational mobile subscriber identity code; and where at least oneselected from the generating and both causing steps are responsive oradditionally responsive to the comparing step.

A system is described for paying for a product or service, the systemincluding a user interface manager having at input for receiving, at afirst time, from a merchant requesting payment from a payment processorthat is a sineroaming roaming services provider, an account identifierfor a user at that merchant, and a telephone number of the user, theuser interface manager for providing at an output the telephone numberreceived at the first time and the account identifier received at thefirst time; a challenge response manager having an input coupled to theuser interface manager output for receiving the telephone numberreceived at the first time, the challenge response manager for verifyingvia an input/output that the user has possession of the telephonecorresponding to the telephone number received at the first time andfor, responsive to the user having possession of said telephone,associating, via an input/output, the telephone number received at thefirst time with the account identifier received at the first time; andwhere the user interface manager is additionally for, at a second time,subsequent to the first time, receiving via the user interface managerinput, the account identifier and an amount from a merchant for theproduct or service, other than roaming or another mobile-related productor service, and additionally for outputting the amount, and accountidentifier or telephone number or both, received at the second time; andwhere the challenge response manager input is additionally for receivingthe account identifier, telephone number or both, received at the secondtime, and the challenge response manager is additionally for determiningvia the challenge response manager input/output whether the telephonenumber was associated with the account identifier, at least one of whichwas received at the second time, and for providing at the challengeresponse manager output an indication responsive to said determining;additionally including a settlement manager having an input coupled tothe user input manager output for receiving the telephone number and theamount, the settlement manager for generating at an output, to a mobiletelephone account corresponding to the telephone number received at thesettlement manager input, a roaming charge responsive to the amount,without the system verifying that said user has possession of saidtelephone between the second time and a time corresponding to thegenerating of the roaming charge, and for causing via the settlementmanager output, the merchant to perform a goods or services action,without the system verifying that said user has possession of saidtelephone between the second time and a time corresponding to thecausing the merchant to perform, and for causing via the settlementmanager output, the merchant to be provided funds responsive to theamount, without the system verifying that said user has possession ofsaid telephone between the second time and a time corresponding to thecausing the merchant to be provided.

The system may additionally operate as follows: the user interfacemanager input is additionally coupled to the challenge response manageroutput for receiving the indication; and the user interface managerprovides the amount and account identifier, telephone number or both, tothe settlement manger responsive to the indication.

The system may additionally operate as follows: the user interfacemanager additionally receives an identifier of the merchant at the userinterface manager input; the user interface manager is additional forproviding the merchant identifier at the user interface manager output;the challenge response manager input is additionally for receiving themerchant identifier; and the challenge response manager additionallyassociates an identifier of the merchant with at least one selected fromthe telephone number and the account identifier.

The system may additionally have, a merchant system having an input forreceiving a user identifier from the user near each of the first timeand the second time, the merchant system for converting the useridentifier received at each of the first time and the second time intothe account identifier, the user identifier received from the user beingdifferent from the account identifier, and for providing the accountidentifier at an output coupled to the user interface manager input, ateach of the first time and the second time.

The system may additionally operate where the merchant system isadditionally for providing at the merchant system output at the firsttime, an indication that the user is being registered.

The system may additionally have an account information retriever havingan input coupled to the user interface manager output for receiving thetelephone number, the account information retriever for obtaining via aninput/output a first international mobile subscriber identity coderesponsive to the telephone number received at the first time and forobtaining a second international mobile subscriber identity coderesponsive to the telephone number received at the second time and forproviding the first international mobile subscriber identity code andthe second international mobile subscriber identity code at an output;and where the challenge response manager input is additionally coupledto the account information retriever output for receiving the firstinternational mobile subscriber identity code and the secondinternational mobile subscriber identity code, the challenge responsemanager is additionally for comparing the first international mobilesubscriber identity code and the second international mobile subscriberidentity code; and the challenge response manager provides theindication additionally responsive to the comparing.

The system may additionally have an account information retriever havingan input coupled to the user interface manager output for receiving thetelephone number, the account information retriever for obtaining via aninput/output a first international mobile subscriber identity coderesponsive to the telephone number received at the first time and forobtaining a second international mobile subscriber identity coderesponsive to the telephone number received at the second time and forproviding the first international mobile subscriber identity code andthe second international mobile subscriber identity code at an output;and where: the challenge response manager input is additionally coupledto the account information retriever output for receiving the firstinternational mobile subscriber identity code and the secondinternational mobile subscriber identity code, the challenge responsemanager is additionally for comparing the first international mobilesubscriber identity code and the second international mobile subscriberidentity code; and the challenge response manager provides theindication additionally responsive to said comparing.

A computer program product is described including a computer useablemedium having computer readable program code embodied therein for payingfor a product or service, the computer program product includingcomputer readable program code devices configured to cause a computersystem to: at a first time, receive by a payment processor that is asineroaming roaming services provider from a merchant different from,not under control of and not controlled by the payment processor, anaccount identifier for a user at that merchant, and a telephone numberof the user as a request for payment to the merchant by the paymentprocessor; verify that the user has possession of the telephonecorresponding to the telephone number received; associate the telephonenumber with the account identifier responsive to the verifying that theuser has possession of said telephone; at a second time, subsequent tothe first time, receive by the payment processor an amount from themerchant for the product or service, other than roaming or anothermobile-related product or service and at least one selected from theaccount identifier and the telephone number; responsive to the accountidentifier or telephone number or both received at second time,determine whether the telephone number was associated with the accountidentifier; generate, to a mobile telephone account corresponding to thetelephone number received, a roaming charge responsive to the amountwithout verifying that said user has possession of said telephonebetween the second time and operation of the computer readable programcode devices configured to cause the computer system to generate; causethe merchant to perform a goods or services action without verifyingthat said user has possession of said telephone between the second timeand operation of the computer readable program code devices configuredto cause the computer system to cause the merchant to perform; and causethe merchant to be provided funds responsive to the amount withoutverifying that said user has possession of said telephone between thesecond time and operation of the computer readable program code devicesconfigured to cause the computer system to cause the merchant to beprovided.

The computer program product may include a feature wherein at least oneselected from the computer readable program code devices configured tocause the computer system to generate and both computer readable programcode devices configured to cause the computer system to cause areresponsive to the computer readable program code devices configured tocause the computer system to determine.

The computer program product may additionally include associating anidentifier of the merchant with at least one selected from the telephonenumber and the account identifier.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to, at themerchant, at each of the first time and the second time: receive a useridentifier from the user; convert the user identifier received into theaccount identifier, the user identifier received from the user beingdifferent from the account identifier; and provide the accountidentifier to a payment processor.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to, at thefirst time, indicate at the merchant that the user is being registered.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to: obtaina first international mobile subscriber identity code responsive to thetelephone number received at the first time; obtain a secondinternational mobile subscriber identity code responsive to thetelephone number received at the second time; and compare the firstinternational mobile subscriber identity code and the secondinternational mobile subscriber identity code; and an additional may beat least one selected from the computer readable program code devicesconfigured to cause the computer system to generate and both of thecomputer readable program code devices configured to cause the computersystem to cause are responsive to the comparing step.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to: obtaina first international mobile subscriber identity code responsive to thetelephone number received at the first time; obtain a secondinternational mobile subscriber identity code responsive to thetelephone number received at the second time; and compare the firstinternational mobile subscriber identity code and the secondinternational mobile subscriber identity code; and an additional featuremay be that at least one selected from the computer readable programcode devices configured to cause the computer system to generate andboth of the computer readable program code devices configured to causethe computer system to cause are responsive or additionally responsiveto the computer readable program code devices configured to cause thecomputer system to compare.

There is disclosed a method of requesting information about a mobilesubscriber telephone account, the method including the steps of:identifying cellular telephone service providers corresponding to acountry code of the telephone number corresponding to the mobilesubscriber telephone account; identifying an order of the cellulartelephone service providers identified, in decreasing order of marketshare figures for each of said cellular telephone service providers; andquerying the cellular telephone service providers for information aboutthe mobile subscriber telephone account, responsive to at least part ofthe order identified.

There is disclosed a method of charging a cellular telephone account forgoods or services purchased by a consumer from a merchant via anInternet, the method including the steps of: identifying a first countryat which the consumer is connected to the Internet; identifying a secondcountry corresponding to a telephone number of a cellular telephone ofthe consumer; identifying a third country corresponding to a location ofthe cellular telephone of the consumer; identifying at least one fourthcountry comprising at one selected from a location of the merchant and adestination for the goods or services; and charging the cellulartelephone account responsive to the first country, the second country,the third country and at least one of the at least one fourth country.

There is disclosed a method of identifying a minimum balance that mustbe maintained by a cellular telephone service provider, including thesteps of: identifying a balance of each of at least one account of thecellular telephone service provider; attempting to make a plurality ofcharges to the at least one account of the cellular telephone serviceprovider; receiving a response to each of the plurality of charges, theresponse comprising an indication of whether the charge was accepted, atleast one of the plurality of charges attempted receiving a responsethat such charge was accepted and at least one of the plurality ofcharges attempted receiving a response that such charge was notaccepted; and identifying the minimum balance responsive to at least onecharge that was accepted at least one charge that was rejected, thebalance identified of at least one of the at least one accountcorresponding to at least one of the at least one the charge that wasaccepted, and the balance identified of at least one of the at least oneaccount corresponding to at least one of the at least one the chargethat was not accepted.

There is disclosed a method of charging a user for goods or servicesbeing purchased from a merchant, the method including the steps of: a)receiving from the merchant an amount of a charge for the goods orservices and a telephone number of a mobile telephone; b) determiningthat an available balance, at a first time, of an account of a mobiletelephone service provider corresponding to the telephone numberreceived is insufficient to supply the amount of the charge; c)responsive to the determining step b), informing the user that thecharge cannot be processed and requesting the user to increase thebalance of the account; d) responsive to the determining step b),instructing the merchant to wait; e) after a period of time, determiningthat an available balance, at a second time, of the account of themobile telephone service provider corresponding to the telephone numberreceived is sufficient to supply the amount of the charge; f) causing atleast the amount of the charge to be deducted from the account; and g)instructing the merchant to perform a goods or services actionresponsive to the causing step or the determining step e).

There is disclosed a method of charging a subscriber's mobile telephoneaccount for two separate purchases of goods or services, including thesteps of: receiving an amount of a first purchase at a first merchant ata first time, and an identifier of an account at a mobile telephoneservice provider; verifying that the account is either creditworthy orcan support the amount of the first purchase; instructing the firstmerchant to perform a goods or services action responsive to theverifying step; receiving an amount of a second purchase at a secondmerchant at a second time, after the first time, and an identifier ofthe account at a mobile telephone service provider; and instructing thesecond merchant to perform a goods or services action without verifyingthat the account is either creditworthy or can support the amount of thesecond purchase.

There is disclosed a method of providing funds to a financial accountfrom an account that is used to pay for a mobile telephone of a user,the method including the steps of: receiving a first amount resultingfrom an action of the user; providing a roaming charge to the accountthat is used to pay for the mobile telephone of the user, the roamingcharge responsive to the first amount; and responsive to the firstamount, providing funds to the financial account having at least anappearance to a merchant of at least one selected from a credit cardaccount and a debit card account.

The first amount may be responsive to an amount provided by a merchant,and the two amounts may be the same or different.

The first amount may be responsive to an amount received from the user.

The method may additionally include the steps of: retrieving an IMSIresponsive to the receipt of the first amount; and comparing the IMSIretrieved to an IMSI previously retrieved; and the providing funds stepmay be additionally responsive to the comparing step

There is disclosed a method of paying for a product other than a mobiledevice-related product or service other than a roaming service, themethod including the steps of: receiving an amount from a merchant forthe product or service, other than the roaming service; receiving atelephone number of a user who will be paying for the product orservice; generating, to a mobile telephone account corresponding to thetelephone number received, a roaming charge responsive to the amount;causing the merchant to perform a goods or services action; and causingthe merchant to be provided funds responsive to the amount.

The method may have the step of checking to ensure the holder of adevice corresponding to the mobile telephone account receives a messagesent to the device; and the causing and providing steps may beresponsive to the checking step.

The method may additionally have th step of checking to see if themobile telephone account has been suspended or disabled; and the causingand providing steps may be responsive to the checking step.

The method may additionally have the steps of: determining whether themobile telephone account is a prepaid account; and responsive to themobile telephone account being determined to be a prepaid account,identifying whether a balance in the mobile telephone account is atleast the amount; and the causing and providing steps may be responsiveto the identifying step.

The method may include that the identifying step includes identifyingwhether the balance in the mobile telephone account is at least theamount and an additional amount corresponding to an operatorcorresponding to the prepaid account.

The method may additionally have the steps of: determining whether themobile telephone account is a prepaid account; and responsive to themobile telephone account being determined not to be a prepaid account,identifying whether a mobile telephone account is in good standing; andthe causing and providing steps may additionally be responsive to theidentifying step.

In the method, the goods or services action may include shipping goodsor performing a physical service.

A system is disclosed for paying for a product other than a mobiledevice-related product or service other than a roaming service, thesystem including a user interface manager having an input forelectronically receiving an amount from a merchant for the product orservice, other than the roaming service and for receiving a telephonenumber of a user who will be paying for the product or service, the userinterface manager for providing the amount and the telephone number atan output; a settlement manager having an input coupled to the userinterface manager output for receiving the amount and the telephonenumber, the settlement manager for generating at an output, to a mobiletelephone account corresponding to the telephone number received at thesettlement manager input, a roaming charge responsive to the amountreceived at the settlement manager input and for causing via thesettlement manager output the merchant to perform a goods or servicesaction, and for crediting, via the settlement manager output, themerchant, responsive to the amount.

The system may additionally include a challenge response manager havingan input coupled to the user interface manager for receiving thetelephone number, the challenge response manager for checking via aninput/output to ensure the holder of a device corresponding to themobile telephone account receives a message sent to the device, and forproviding at an output coupled to the user interface manager input anindication responsive to said holder corresponding to said amount; andin the system, the settlement manager may generate the roaming charge,cause the merchant to perform the goods or services action, and creditthe merchant responsive additionally responsive to the indication.

The system may additionally include a fraud manager having an inputcoupled to the user input manager output for receiving the telephonenumber, the fraud manager for checking via an input/output to see if themobile telephone account has been suspended or disabled and forproviding at an output coupled to the user interface manager input anindication responsive to said account being suspended or disabled; andthe settlement manager may generate the roaming charge, cause themerchant to perform the goods or services action, and credit themerchant, additionally responsive to the indication.

The system may additionally include: a prepaid determination managerhaving an input coupled to the user interface manager output forreceiving the telephone number, the prepaid determination manager fordetermining via an input/output whether the mobile telephone account isa prepaid account and for providing at an output coupled to the userinterface manager input a first indication responsive to said mobiletelephone account being a prepaid account; and a balance sufficiencymanager having an input coupled to the user interface manager output forreceiving the telephone number and the amount responsive to theindication corresponding to the mobile telephone account being a prepaidaccount, the balance sufficiency manager for identifying via aninput/output whether a balance in the mobile telephone account is atleast the amount and for providing at an output coupled to the userinterface manager input a second indication responsive to said mobiletelephone account identified as being at least the amount; and, thesettlement manager may generate the roaming charge, cause the merchantto perform the goods or services action, and credit the merchant,additionally responsive to the first and second indication.

In the system, the balance sufficiency manager may identify whether thebalance in the mobile telephone account is at least the amount of thecharge responsive to the balance in the mobile telephone account beingat least the amount and an additional amount corresponding to anoperator corresponding to the prepaid account.

The system may additionally include: a prepaid determination managerhaving an input coupled to the user interface manager output forreceiving the telephone number, the prepaid determination manager fordetermining via an input/output whether the mobile telephone account isa prepaid account and for providing at an output coupled to the userinterface manager input a first indication responsive to said mobiletelephone account not being a prepaid account; and a creditworthymanager having an input coupled to the user interface manager output forreceiving the telephone number and the amount responsive to the firstindication corresponding to the mobile telephone account not being aprepaid account, the creditworthy manager for identifying via aninput/output whether a subscriber of the mobile telephone account isworthy of credit for the amount and for providing at an output coupledto the user interface manager input a second indication responsive tosaid subscriber of mobile telephone account being worthy of credit forthe amount; and the settlement manager may generate the roaming charge,cause the merchant to perform the goods or services action, and creditthe merchant, additionally responsive to the first and secondindication.

There is disclosed a computer program product including a computeruseable medium having computer readable program code embodied thereinfor paying for a product or service other than a roaming service, thecomputer program product comprising computer readable program codedevices configured to cause a computer system to: receive an amount froma merchant for the product or service, other than the roaming service;receive a telephone number of a user who will be paying for the productor service; generate, to a mobile telephone account corresponding to thetelephone number received, a roaming charge responsive to the amount;cause the merchant to perform a goods or services action; and cause themerchant to be provided funds responsive to the amount.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to check toensure the holder of a device corresponding to the mobile telephoneaccount receives a message sent to the mobile telephone corresponding tothe telephone number; and the computer readable program code devicesconfigured to cause the computer system to cause and provide may beresponsive to the computer readable program code devices configured tocause the computer system to check.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to check tosee if the mobile telephone account has been suspended or disabled; andthe computer readable program code devices configured to cause thecomputer system to cause and provide may be responsive to the computerreadable program code devices configured to cause the computer system tocheck.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to:determine whether the mobile telephone account is a prepaid account; andresponsive to the mobile telephone account being determined to be aprepaid account, identify whether a balance in the mobile telephoneaccount is at least the amount; and the computer readable program codedevices configured to cause the computer system to cause and provide maybe responsive to the computer readable program code devices configuredto cause the computer system to identify.

In the computer program product, the computer readable program codedevices configured to cause the computer system to identify may includecomputer readable program code devices configured to cause the computersystem to identify whether the balance in the mobile telephone accountis at least the amount and an additional amount corresponding to anoperator corresponding to the prepaid account.

The computer program product may additionally include computer readableprogram code devices configured to cause the computer system to:determine whether the mobile telephone account is a prepaid account; andresponsive to the mobile telephone account being determined not to be aprepaid account, identify whether a mobile telephone account is in goodstanding; and computer readable program code devices configured to causeand provide may be responsive to the computer readible program codedevices configured to cause the computer system to identify.

In the computer program product, the goods or services action mayinclude shipping goods or performing a physical service.

1-21. (canceled)
 22. A method of detecting a potentially fraudulenttransaction involving a communications device, comprising: obtaining apayment record of a subscriber in possession of the communicationsdevice from a merchant; obtaining, from the merchant, a transactionidentifier of a transaction entered into by the subscriber in possessionof the communications device; determining whether a fraud score meets orexceeds a threshold; and identifying the transaction as fraudulent basedon the determination that the fraud score meets or exceeds thethreshold.
 23. The method of claim 22, wherein determining whether thefraud score meets or exceeds the threshold comprises: comparing acountry in which the subscriber is currently located with the country inwhich the merchant is currently located.
 24. The method of claim 22,wherein determining whether the fraud score meets or exceeds thethreshold comprises: comparing the transaction identifier from themerchant and the subscriber with corresponding entries of a registeredsubscriber table.
 25. The method of claim 22, further comprising, priorto obtaining the payment record from the merchant, registering a mobilesubscriber with an account controlled by the merchant.
 26. The method ofclaim 25, further comprising associating the communications device withthe merchant responsive to the communications device registering withthe merchant.
 27. The method of claim 22, further comprising obtainingresults of a comparison of a challenge phrase entered by subscriber ofthe communications device with the challenge phrase generated by achallenge response manager.
 28. The method of claim 27, comprisingverifying, by the challenge response manager, that an internationalmobile subscriber identifier (IMSI) in the payment record matches anIMSI associated with the transaction identifier.
 29. The method of claim22, wherein determining whether the fraud score meets or exceeds thethreshold comprises determining whether one or more credit cardchargebacks have occurred with respect to an account held by thesubscriber.
 30. The method of claim 29, further comprising determiningwhether the one or more credit card chargebacks have occurred within aspecified period of time.
 31. The method of claim 29, further comprisingdetermining whether at least one of the one or more credit cardchargebacks involves at least a threshold monetary amount.
 32. Themethod of claim 22, further comprising determining that a timestamp ofthe payment record does not differ from the current date and time bymore than a threshold amount.
 33. An apparatus to detect a potentiallyfraudulent transaction, comprising: a processor, coupled to at least onememory device, to: receive, from a merchant, a record to indicate apayment made to the merchant by a subscriber in possession of acommunications device; determine, in response to an outcome of acomparison made between the record to indicate the payment and anidentifier associated with the merchant, a fraud score of thecommunications device; and to permit the potentially fraudulenttransaction to occur based, at least in part, on whether the determinedfraud score is less than a threshold level.
 34. The apparatus of claim33, wherein the processor coupled to the at least one memory device isadditionally to register a mobile subscriber with an account controlledby the merchant prior to receiving the record to indicate the paymentmade by the subscriber in possession of the communications device. 35.The apparatus of claim 34, wherein the processor coupled to the at leastone memory device is additionally to associate the communications devicewith the merchant responsive to registration of the communicationsdevice with the merchant.
 36. The apparatus of claim 35, wherein theprocessor coupled to the at least one memory device is additionally toobtain results of a comparison of a challenge phrase entered by thesubscriber of the communications device with the challenge phrasegenerated by a challenge response manager.
 37. The apparatus of claim36, wherein the processor coupled to the at least one memory device isadditionally to verify, by the challenge response manager, that aninternational mobile subscriber identifier (IMSI) in the record matchesan IMSI associated with the identifier associated with the merchant. 38.The apparatus of claim 33, wherein the processor coupled to the at leastone memory device is additionally to determine whether one or morecredit card chargebacks have occurred with respect to an account held bythe subscriber.
 39. The apparatus of claim 38, wherein the processorcoupled to the at least one memory device is additionally to determinewhether the one or more credit card chargebacks have occurred within aspecified period of time.
 40. The apparatus of claim 38, wherein theprocessor coupled to the at least one memory device is additionally todetermine whether at least one of the one or more credit cardchargebacks involves at least a threshold monetary amount.
 41. Theapparatus of claim 38, wherein the record comprises a phone number tocorrespond to the communications device.
 42. The apparatus of claim 33,wherein the processor coupled to the at least one memory device isadditionally to determine that a timestamp of the record does not differfrom the current date and time by more than a threshold amount.